[Subclipse-users] Extremely slow performance in Subclipse method StatusCacheManager.basicGetStatus()

Hi Subclipse Community,

Im experiencing extremely slow performance when starting Eclipse with
a project containing the Scala programming language's main source tree
checked out [http://lampsvn.epfl.ch/svn-repos/scala/scala/trunk].

Eclipse has run at 100% CPU for more than 2 hours, with the message
"Initializing Java Tooling (59%)" showing.

By use of a debugger, I have learned that:

* The delay is caused by a massive amount of time spent within
org.tigris.subversion.subclipse.core.status.StatusCacheManager.basicGetStatus()

* Eclipse is not stuck, or hung or in an infinite loop. By
periodically remaining stack variables, I can see it *is* progressing
over files in the source tree, just very slowly.

* By random sampling, I believe most time is being spent in these two
methods, within StatusCacheManager.basicGetStatus():
  - org.tigris.subversion.javahl.SVNClient.status(java.lang.String,
int, boolean, boolean, boolean, boolean, java.lang.String[],
org.tigris.subversion.javahl.StatusCallback) line: not available
[native method]
  - java.io.WinNTFileSystem.checkAccess(java.io.File, int) line: not
available [native method]

* No Scala-related code is executing in the slow thread, its all
Subclipse/Subversion.

Now, the Scala project does contain a *very* large number of files.
However, startup times in excess of 2 hours render Eclipse unusable in
practice.

Environment: Win Vista, Java 1.6.12, Eclipse 3.4.1, Subclipse 1.4.7

Some questions:
* Is this a known issue?
* Are there any algorithms in Subclipse that are worse than linear in
terms of the number of files in the project?
* What I can do to assist resolving this bottleneck?

Thank you
Ben

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=1223099

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-02-24 23:58:05 CET