I am pretty sure there are many more things that can slow Eclipse down, like number of open projects, background processes, and bad Eclipse performance that should be resolved with Kepler.
Of course there are variables that can slow down or Eclipse IDE. Mainly the number of projects open, the local server, etc etc. I just find it useful having this Heap parameter and showing us memory usage. My computer has only 4gig. and I can see it being sluggish when having many app open.
You can try to increase the heap of your Eclipse JVM, giving Eclipse more space and decreasing the need of GC. As many programs, Java tries to make efficient use of the available RAM. Allocated but not used RAM is something Java tries to fill with content. After running a GC, how much time does it take for Eclipse to fill it up again?
I am pretty sure there are many more things that can slow Eclipse down, like number of open projects, background processes, and bad Eclipse performance that should be resolved with Kepler.
So, does running GC really help?
Hi Tobias,
Of course there are variables that can slow down or Eclipse IDE. Mainly the number of projects open, the local server, etc etc. I just find it useful having this Heap parameter and showing us memory usage. My computer has only 4gig. and I can see it being sluggish when having many app open.
What is Kepler? I never heard of this before.
Cheers Nick.
Eclipse Kepler: http://www.eclipse.org/downloads/index-developer.php
Eclipse Release 4.3.
You can try to increase the heap of your Eclipse JVM, giving Eclipse more space and decreasing the need of GC. As many programs, Java tries to make efficient use of the available RAM. Allocated but not used RAM is something Java tries to fill with content. After running a GC, how much time does it take for Eclipse to fill it up again?