I've checked out the code. I think it was about 50 MB. I did not
encounter any problems. After checkout the decorators were present
almost instantly. I even used an existing workspace with about 20
other decent sized projects just in case it mattered.
I used a pretty similar setup to you. Vista, Eclipse 3.4.0 and Java
1.6.10 with Subclipse 1.4.7. I think I am using the Eclipse "Classic
SDK" with no extras other than Mylyn and Subclipse.
One thing that occurs to me, as others have had problems like this in
the past ... are you running builds outside of Eclipse, such as using
Ant? This can cause performance problems as the build creates a ton
of new files that Eclipse does not know about. When the workspace
refreshes and it discovers them it sends a flood of resource changes
through the system and it can take a while to process all of those.
We've done most of the optimizations we can, I actually thought the
problem was resolved as I do not recall hearing it lately. I am just
speculating anyway since I am not seeing a problem. So just trying to
think what else we could look for.
On Tue, Feb 24, 2009 at 8:46 PM, Mark Phippard <markphip_at_gmail.com> wrote:
> How big is it? I'll check it out to see what happens, but would like
> to know how much it is going to checkout.
> What you are seeing does not sound normal.
> On Tue, Feb 24, 2009 at 5:54 PM, ben_hutchison <ben_at_playscapegames.com> wrote:
>> 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
>> * 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
>> Now, the Scala project does contain a *very* large number of files.
>> However, startup times in excess of 2 hours render Eclipse unusable in
>> 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
>> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
> Mark Phippard
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-02-28 21:16:17 CET