On Thu, Apr 5, 2012 at 6:43 PM, Brock Janiczak <brockj@...> wrote:
> I have recently started using Subclipse (v1.8) again and have run into
> unacceptable performance on one of my projects.
That is disappointing to hear. We actually think performance is
substantially improved across the board. We have significantly
improved the cache management and eliminated virtually all unnecessary
refreshes and fetches. And of course SVN 1.7 is generally faster too.
> 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
There have been changes made in the last couple release related to
hiding the duplicates in this scenario. Maybe the Eclipse calls that
entails cause additional work to be done?
> A lot of time is spent on File.exits and reading from the v3 cache
Can you elaborate?
> 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?
We spent significant time considering that option and ruled it out.
Your working copy is not by chance stored on a network mount is it?
That is one area where SVN 1.7 has some significant performance