[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[Subclipse-dev] Slow SVN cache updates

From: Brock Janiczak <brockj_at_gmail.com>
Date: Fri, 6 Apr 2012 08:43:58 +1000

I have recently started using Subclipse (v1.8) again and have run into
unacceptable performance on one of my projects. Refreshing the
workspace can take several hours for a workspace that only contains
under 100mb of files. I have collected a yourkit profile and will
investigate further next week

The only thing odd about my setup is that i am using maven 2 and have
a nested project structure where i have one project that contains all
sub modules and i also create top level projects pointing to resources
in the top level project. ie:
Main Project
-Sub Directory 1
-Sub Directory 2
Sub Directory 1 Project
Sub Directory 2 Project

A lot of time is spent on File.exits and reading from the v3 cache
file. Heaps of time is spent allocating and garbage collecting too
and CPU usage is quite low (15% on my 4 core i7)

Since 1.8 uses svn 1.7, would it make sense to no longer use the
status cache and just call the WC api to get the status?



To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_subclipse.tigris.org].
Received on 2012-04-06 01:11:40 CEST

This is an archived mail posted to the Subclipse Dev mailing list.