[Typo3-dev] HINT: speed up eclipse

[Rainer Kuhn]

Ingo Renner wrote:

> Hi all,
> 
> this is a small hint for all of us using eclipse. To speed up eclipse -
> especially the startup
> 
> modify your shortcut like this:
> C:\Programme\eclipse31\eclipse.exe -vmargs -Xmx128m -Xms128m
> 
> notice the added arguments, the 128 can be replaced by any value. It
> defines the amount of memory eclipse allocates directly on startup instead
> of doing it _during_ startup or work with eclipse. If you have a lot of
> memory you can set this to 256 or even more if necessary.

Some more explanations I've found formerly concerning this topic:

This is about tuning the JVM heap size which can help to improve 
Eclipse's responsiveness. You can do that by using the -vmargs -Xms -Xmx 
settings in the command-line argument:
-Xms is your minimum JVM memory size.
-Xmx is your maximum JVM memory size.
The values to set depend on the specifications of the system you are 
working on. Most of the posts I have seen talk about setting the max. 
heap size to at least 256M.


 From the Eclipse Project Release Notes 3.0.1:
"Depending on the JRE that you are running, the number of plug-ins you 
are using, and the number of files you will be working with, you may 
have to increase the amount of memory that is available to the Java VM 
running Eclipse. Eclipse allows you to pass arguments directly to the 
Java VM using the -vmargs command line argument, which must follow all 
other Eclipse specific arguments. To increase the available memory, you 
would typically use:

     eclipse -vmargs -Xmx<memory size>

The <memory size> value should typically be at least "128M" (128 
megabytes). Usually, "256M" (256 megabytes) is ample. You should not set 
this value to be larger than the amount of physical memory on your machine."


For detailled hints on tuning the Eclipse JVM heap size, you can refer 
to this IBM article: 
http://www-128.ibm.com/developerworks/websphere/library/techarticles/0204_searle/searle.html


HTH,
Rainer