- This topic has 9 replies, 3 voices, and was last updated 19 years, 4 months ago by
.
-
Posts
-
Hello,
I have installed a trial of MyEclipse 4 Milestone 2 (Build: 20050627-4.0-Milestone-2) and when using the JSP-Editor and using any kind of CodeCompletion (finding methods or so) it is incredibly slow (I have to wait about 30 seconds while nothing happens in the IDE!). Please help, as this feature is definitely not usable actually.
I have a Windows-Computer with 1 Gig of mem, which I think should be enough!
Bye, Zeljko
Zeljko,
What version of Eclipse are you using? (Help > About)Also what JDK are you using to run Eclipse with?
What command line arguments are you using to start MyEclipse? If you are not using command line arguments, it is not surprising autocomplete is very slow, we would suggest using -vmargs -Xmx256m atleast.
Also what speed is your processor?
I’m using -vmargs -Xmx512M and JDK 1.4.2_07 with the newest version of Eclipse (3.1) BuildId: I20050627-1435.
Processor speed?
Also, how many JARs do you have in your classpath for your project under Java Build Path > Libraries (under project properties)
45 jars
Ahh, this is the problem. Try and remove all the JARs from your classpath that you do not need for compile-time dependencies. All of them are runtime deps, but likely only 20% of them are compile-time deps. When you invoke autocomplete it has to index and lookup from all those 45 JARs that can contain 1000s of classes.
Hi,
Ok, I can try to figure out, which one is not needed during compile time, but as Eclipse compiles the whole project after removing one, this seems to be a very annoying task. And as Eclipse usually (after importing a project) uses a build path with all libraries of the project this is not a good solution.
Eclipse’s Java-Editor code completion can usually handle all these jars as well without being so slow, so I think this not efficiently programmed. Maybe a feature that is to be refactored in future releases. For me – and maybe for others – the other very powerful features (J2EE-Deployment) are not of such great interest in the current project, as we have already a deployment script with ant.
Bye, Zeljko
Zeljko,
I should have clarified that my suggestion was a workaround, I agree that this is a performance issue we should look into.I’m also noticing a MAJOR slow down in JSP compilation between version 3.7.2 and 3.8.4
The only thing I did was upgrade from MyEclipse 3.7.2 to 3.8.4.
I made absolutely no other changes.
The JSP editor did change between the 3.7.x series and 3.8, that was the first release we built ontop of WTP, given the early stages of WTP I think there are still quite a few kinks they need to work out that will in response help stabalize/speed up MyEclipse considerably. We are also investigating this internally.
