Eclipse Startup Run Speed tuning

JVM switches to improve the performance of the JAVA IDE

Submitted by small Scorpio on the August, 2:45 PM. Integration

My laptop is P4 1.8G Dell c640 Memory 1g,eclipse 3.1 + myeclipse 4.0m2 speed is good.

The running parameters are as follows:

eclipse.exe-vmargs-xverify:none-xx:+useparallelgc-xx:permsize=20m

－－－－－－－－－－－－－－

The JVM provides a variety of standard switches and non-standard switches for adjusting memory allocation and garbage collection behavior. Some of these settings can improve the performance of the JAVA IDE.

Note that because-X (especially-XX JVM) switches are usually specific to the JVM or JVM vendor, the switches described in this section can be used for Sun Microsystems J2SE 1.4.2.

The following settings will produce better setup performance than the factory on most systems.

-vmargs-Indicates that all subsequent parameters are passed directly to the indicated Java VM.

-xverify:none-This switch turns off Java bytecode validation, which speeds up class loading and eliminates the need to mount classes for validation purposes only. This switch shortens startup time, so there's no reason not to use it.

-xms24m-This setting instructs the Java virtual machine to set its initial heap size to MB. By indicating the amount of memory that the JVM should initially allocate to the heap, you can make the JVM do not have to increase the heap size when the IDE consumes more memory.

-xmx96m-This setting specifies the maximum amount of memory the Java virtual machine should use for the heap. Setting the upper limit for this quantity indicates that the Java process consumes no more than the amount of physical memory available. This limit can be increased for systems with more memory, and the MB setting helps ensure that the IDE can reliably perform operations on a system that has an inventory of 128MB to 256MB. Note: Do not set this value to be close to or larger than the physical memory of the system, or it will cause frequent swap operations during the primary recovery process.

-xx:permsize=20m-This JVM switch is not only more powerful, but it can shorten startup time. This setting adjusts the size of the memory "permanent Zone" (the class is saved in the zone). So we hint to the JVM what amount of memory it will need. This setting eliminates many of the major garbage collection events during system startup. Users of SunOne Studio or other Ides that contain more modules may want to set this number higher.

Some other JVM switches that may have a slight or significant impact on the performance of ECLIPSE on some systems (not all systems) are listed below. While using them can have a certain impact, it is still worth a try.

-XX:COMPILETHRESHOLD=100-This switch will slow down the boot speed because HotSpot can compile more methods into local code faster than not using this switch. The result is improved performance for the IDE at run time because more UI code will be compiled rather than interpreted. This value represents the number of times the method must be invoked before being compiled.

-XX:+USECONCMARKSWEEPGC-XX:+USEPARNEWGC-Try using these switches if the garbage collection is frequently interrupted. This switch causes the JVM to use different algorithms for primary garbage collection events, if they are running on multiprocessor workstations, and for secondary recycle events, and these algorithms do not affect the entire garbage collection process. Note: It is not yet certain that this collector is improving or reducing the performance of a single-processor computer.

-XX:+USEPARALLELGC-some tests show that, at least in a single-processor system with a fairly good memory configuration, this collection algorithm can be used to halve the duration of a secondary garbage collection. Note that this is a contradictory issue, in fact this collector is primarily suitable for multiprocessor with a gigabit heap. There is no data available to indicate its impact on primary garbage collection. Note: This collector is mutually exclusive with the-XX:+USECONCMARKSWEEPGC.

My machine is 512MB of RAM

Here's my eclipse startup parameters: ECLIPSE.EXE-VMARGS-XVERIFY:NONE-XMS64M-XMX256M-XX:PERMSIZE=20M-XX:+USEPARALLELGC

-----

by Beansoft:

My computer is 1G memory, there is not enough memory at once ... MyEclipse recommended me to use a startup parameter, and now my startup parameters are:

Eclipse.exe-vmargs-xverify:none-xms128m-xmx512m-xx:permsize=64m-xx:maxpermsize=128m-xx:+useparallelgc