Eclipse Juno + WTP +EGit dead slow

Question

I'm trying to use Eclipse Juno (Version: 4.2.0 Build id: I20120608-1400) with WTP for JavaScript/Node.js development on MacOSX Lion, on my 4GB RAM MacBook Pro. Sometimes it gets dead slow, and unusable. I've tried tweaking both through preferences (disabled all validators) and initialization variables, and also upgraded to 1.7 VM as recommended. Here's the contents of my eclipse.ini file:

-startup
../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20120522-1813.jar
--launcher.library
../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.200.v20120522-1813
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
-vm
/Library/Java/JavaVirtualMachines/1.7.0.jdk/Contents/Home/bin/java
-vmargs
-Xms64m
-Xmx256m
-Xdock:icon=../Resources/Eclipse.icns
-XstartOnFirstThread
-Dorg.eclipse.swt.internal.carbon.smallFonts
-XX:+UseParallelGC
-XX:+UseCompressedOops
-XX:MaxPermSize=256m
-server

Can someone advise what I could do to improve WTP performance?

Answer 1

Found a a bug report (id : 385272) raised for slow Juno response times.

Answer 2

For me, the issue is only happening in the PHP perspective. Launching Eclipse Juno in a different perspective and then switching to the PHP perspective made the tab switching reasonable.

A less cumbersome and permanent solution exists, which is quite straightforward. Installing Web Development Tools fixes this issue.

Answer 3

unfortunately i can second that. juno is unusable slow in comparison to indigo. with every click i have to wait multiple seconds for a reaction of the gui. i too can exclude the reason might be on the side of my hardware.

Answer 4

I have found an unofficial patch, which makes switching between editors a lot faster. See this comment: https://bugs.eclipse.org/bugs/show_bug.cgi?id=391868#c28

You just add the referenced page http://www.objectteams.org/EclipsePatch422beta/, and it seems to be a lot faster. Unofficial patch, so backup your Eclipse before.

Answer 5

You should disable validation of your Node.js and other JavaScript libs as they should be validated by their providers. Try this: https://stackoverflow.com/a/19909401/1040124

Answer 6

I encounter the same issue, and seems to be solved by select the checkbox "Use virtual memory mapping", you can see the option on, Preference-->Team-->Git-->Window Cache