| Eclipse 3.2.2 frequently "pausing" [message #210842] |
Tue, 15 May 2007 18:27  |
Eclipse User |
|
|
|
Hi Everyone,
I've just convinced my development team to accept a new eclipse
development setup, but they've hit a snag.
Every 10 minutes or so, their eclipse just "hangs" for about 10-15
seconds. It's apparently very busy doing something in the background,
judging by the 100% cpu and frequent garbage collection, but I can't
figure out what.
Can anyone tell me what this activity might be? Or how to stop it?
Otherwise I might be threatened by a mutiny :-)
The useful details are:
Eclipse 3.2.2, the latest build off the website. The runtime (and
compiler) are both JDK 1.5.0_06. The desktop is windows XP, 1GB RAM,
pentium 4, roughly 2.4GHz.
Auto-builds are switched OFF.
We do have the sysdeo tomcat plug-in (3.2) but I've since closed the
tomcat project and removed it from some workspaces with no effect. None
of the guys are currently using it anyway.
The standard workspace defines two user libraries. One ("Dev_Libs")
refers to about 20 utility libs (jar files) on the local file system, the
other user library ("Build_Classes") links to a large local jar file of
pre-built classes with a large local source attachment (~7500 classes).
The main java project refers to these two user libs but doesn't reference
any other stray jar files of its own. Some developers have in the order
of ~100 java files checked out locally in a single source directory (it's
actually linked to a directory on a shared drive, but there seems to be no
network traffic during the pauses so that might be a red herring)
My gut feeling is that some sort of automatic build is going on - if I do
a clean build we see the same behaviour for the same period of time. But
automatic builds are switched off.
So I'm stuck.
Thanks :-)
|
|
|
|
| Re: Eclipse 3.2.2 frequently "pausing" [message #211128 is a reply to message #210842] |
Thu, 17 May 2007 15:42  |
| Eclipse User |
|
|
|
Matthew Wilson wrote:
> Hi Everyone,
>
> I've just convinced my development team to accept a new eclipse
> development setup, but they've hit a snag.
>
> Every 10 minutes or so, their eclipse just "hangs" for about 10-15
> seconds. It's apparently very busy doing something in the background,
> judging by the 100% cpu and frequent garbage collection, but I can't
> figure out what.
> Can anyone tell me what this activity might be? Or how to stop it?
> Otherwise I might be threatened by a mutiny :-)
>
> The useful details are:
>
> Eclipse 3.2.2, the latest build off the website. The runtime (and
> compiler) are both JDK 1.5.0_06. The desktop is windows XP, 1GB RAM,
> pentium 4, roughly 2.4GHz.
>
> Auto-builds are switched OFF.
> We do have the sysdeo tomcat plug-in (3.2) but I've since closed the
> tomcat project and removed it from some workspaces with no effect. None
> of the guys are currently using it anyway.
>
> The standard workspace defines two user libraries. One ("Dev_Libs")
> refers to about 20 utility libs (jar files) on the local file system,
> the other user library ("Build_Classes") links to a large local jar file
> of pre-built classes with a large local source attachment (~7500 classes).
> The main java project refers to these two user libs but doesn't
> reference any other stray jar files of its own. Some developers have in
> the order of ~100 java files checked out locally in a single source
> directory (it's actually linked to a directory on a shared drive, but
> there seems to be no network traffic during the pauses so that might be
> a red herring)
>
> My gut feeling is that some sort of automatic build is going on - if I
> do a clean build we see the same behaviour for the same period of time.
> But automatic builds are switched off.
>
> So I'm stuck.
> Thanks :-)
>
>
>
This doesn't address the possibility of unwanted auto-builds, but you
might want to edit eclipse.ini and jack up the heap size. The default
allocation is only 40MB initial/256MB max. If it really is garbage
collection, that should reduce either the duration or frequency of
navel-gazing. Contrapositively, if the change has no effect, something
other than GC is going on.
/Paul
|
|
|
|
|
|
|
| Re: Eclipse 3.2.2 frequently "pausing" [message #212592 is a reply to message #212279] |
Tue, 29 May 2007 08:26 |
| Eclipse User |
|
|
|
Matthew Wilson wrote:
> Ok - I think I've made some progress with this.
>
> We were able to reproduce a serious eclipse lock-up by hitting ctrl-o
> to open the "quick outline" pop-up, then hitting ctrl-o again to see
> inherited features. That was taking several minutes of 100% CPU to
> respond. I got a couple of thread dumps and noticed that a lot of
> activity was occuring within the method:
>
> org.eclipse.jdt.internal.ui.text.JavaOutlineInformationContr ol.toggleShowInheritedMembers()
>
>
> So I added a line to the method:
>
> org.eclipse.jdt.internal.core.JarPackageFragmentRoot.getJar( )
> That would print out some information about which jars were being
> opened. What I discovered is that an ENORMOUS amount of time was
> spent repeatedly interrogating a couple of big jar libraries - one was
> development_classes.jar (our baseline build) and the other was rt.jar
> (from the JDK).
>
> When I unpacked development_classes.jar into a directory and used that
> as a library instead of the jar file, the response times dropped
> considerably. Always one to recognise a good thing when I see it, I
> also tried the same trick on rt.jar and I found that the response
> times dropped to zero (more or less). One of my developers has been
> using this setup now for a couple of days and he says his frequent and
> horrific pauses have disappeared.
>
> So I think I'm out of the woods. But I also think that a real
> performance problem within eclipse could be resolved if that
> "JavaOutlineInformationControl" class (or whatever it's calling) used
> a cleverer way of gathering class information from jar files. It
> seems to do an awful lot of redundant work with zip files. For a few
> small libs it might be fine as it is, but it doesn't appear to scale
> well.
The JavaOutlineInformationControl uses the Java Model. Which in this
case seems to do more work than needed. Please file a bug report with
your findings. Also, can you check whether the same problem appears with
3.3 RC2?
Dani
>
> I'm tempted to do it myself, but this is looking like a very busy
> fortnight coming up. If I get time, I'll have a look.
>
> Thanks everyone.
>
> Matt.
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.11894 seconds
Home