- This topic has 18 replies, 6 voices, and was last updated 19 years, 5 months ago by
.
-
Posts
-
Hi Riyad,
sorry, not an easy answer for you 😉 – I have just 400 java classes, and 100 jsps. I have maybe at most 20 jar files in my classpath if that makes any difference, but these are mostly jre, j2ee, junit, and apache-commons jar files. None of them have source code associated with them.
Mark
Mark,
Please remove ALL the Jars that you don’t need for compile-time dependencies from your build path. We had a user with a very small (50 files) project report insanely long debugging cycles, it turned out he had 50 JARs in his classpath, keep in mind that every single one of these classes have to become “known” to the debugger incase of a breakpoint, stack trace, etc. Once he trimmed down his classpath to only 5 JARs he needed for the compile time deps, everything was snappy as can be.Hi Riyad,
I reduced the the number of jar files in the compile time dependencies from 10 to 6 in the EJB project, 16 to 8 in the library project and 20 to 14 in the web project. This represents a removal of 18 classpath entries out of 46. This isn’t quite the full story, because in each project, 2 of those entries are the JRE library and the J2EE library which I couldn’t remove.
Although it seems to have done the trick (test times is now down to 20 minutes), people have been reporting that this problem is intermittent, so more testing will confirm that all is fine.
It makes sense to pare back my compile dependencies, but I wouldn’t have been expecting such a dramatic change between the version of MyEclipse for Eclipse 3.1 and Eclipse 2.1.
Thanks!
Mark
Mark,
I agree that this is more of a speed impact than we would have liked to see, I think some slowdown is expected as the Eclipse JDT has grown in complexity from 2.x to 3.1 many fold, but I have still filed an issue for us to look into debugger performance just incase there is something we can do to help this in a future release.
