In a quick pointer from Eric's Agile Answers, the author talsk about some of the tweals that made to his Eclipse IDE's JVM runtime parameters in an attempt to boost the IDE's performance on Windows. "I spent some time tweaking my Eclipse IDE's JVM runtime parameters in an attempt to avoid the frustrating memory & harddisk thrashing that I encounter on an occasional (three times a day?) but frustratingly consistent basis. I'm developing on a single CPU (dual core) 64-bit box with 2G of memory and 32-bit Windows XP installed. Here are the eclipse.ini settings I found to work best with the Sun JVM runtime:
he mentions that he not set -Xmx or -Xms values for the heap size intentionally. "According to the JRE docs setting these parameters will disable self-tuning and the JRE seems to do a fine job when allowed to self-tune", he says.
He also points to two Eclipse plugins that he has installed:
KeepResident - Fights undesired memory swapping. "Windows has this nasty habit of swapping out 99% of the process memory when an application is minimized or the mouse cursor leaves the window. All of those page faults that occur when you go back to Eclipse cause it to be really slow and laggy."
MemoryManager - Proactively invokes the Eclipse JRE garbage collector and provides a handy memory monitoring view.