(RPM) Introduction to eclipse startup parameters (such as when adding plug-ins, if not displayed, start with Eclipse-clean)

This article was reproduced from: http://hi.baidu.com/dd_taiyangxue/blog/item/08950f3991b4e8c9d46225c8.html

In fact, Eclipse is a system that can be very flexible to configure, in addition to starting by default, you can also specify a variety of parameters to customize the startup mode. After referencing some of the information, I summed up some of the more commonly used start-up command Arguments, if there is an incorrect place for you to point out.

-arch [Processor architecture]
Description: Specifies the category of the processor being used
Example: Eclipse-arch x86 or Eclipse-arch SPARC

-application [ID]
Description: Specify the app to run with the extension ID plus the extension IDs for the extended org.eclipse.core.applications extension point ID
For example, if you have a plugin ID of Edu.sdu.app and the extension ID is MyApp, then Eclipse-application Edu.sdu.app.myapp will execute your extended application

-clean
Description: Emptying the plugin cache content
For example: Eclipse-clean, sometimes the plugin does not show up because eclipse caches the plug-in to speed up the boot process, and if specified this parameter empties the cache and loads it from the beginning

-configuration [Cofigfile Location]
Description: Specify the location of the configuration file to start using the profile Config.ini under this directory at startup
Example: Eclipse-configuration d:/eclipse/configuration

-data [Workspace Location]
Description: Specifies the workspace location at startup
Examples: For example, if the workspace location is located in D:/myworkspace, then Eclipse-data d:/myworkspace

-debug [option file]
Description: Starts eclipse in the debug state, and all debug switches are specified in the. options file
Example: Eclipse-debug d:/eclipse/.options

-dev [Classpath Entry]
Description: Launches eclipse in development state, which adds all specified paths as classpath for each plug-in
Example: Eclipse-dev bin, which loads all classes generated in the bin directory into the classpath, is useful when developing plug-ins

-nosplash
Description: Specifies that the splash screen is not displayed at startup
Example: Eclipse-nosplash

-VM [JRE Path]
Description: Specifies the Java virtual machine to be used at startup
Example: To use your own Java Virtual machine, eclipse-vmd:/j2sdk1.4.2_04/jre/bin/ Java.exe, there is also a benefit, that is, you can open a console to display console information, of course, if you use ECLIPSE-VM D:/j2sdk1.4.2_04/jre/bin/javaw.exe will not show the console

-vmargs [Java VM arguments]
Description: Specifies the Java Virtual machine parameters to be used at startup
Example: To specify the amount of memory used, Eclipse-vmargs "-xms256m-xmx1024m"
Note: This parameter must be placed on the last side of all parameter variables

If you think your eclipse is slow to start (say more than 20 seconds), maybe you need to tweak your eclipse startup parameters, here are some ' tips ':

1. Check the JVM settings that started eclipse. In help\about Eclipse sdk\configuration detail, you can see the JVM that started eclipse. This JVM is different from the installed JDK you set up in Eclipse. If the JVM that launches eclipse is still JDK 1.4, it is better to change to JDK 5, because JDK 5 has better performance than 1.4.

C:\eclipse\eclipse.exe -vm "C:\Program Files\Java\jdk1.5.0_08\ bin\javaw.exe"

2. Check the size of the heap used by eclipse. There is a profile Eclipse.ini under the C:\eclipse directory, which configures the default heap size for Eclipse startup

-vmargs
-Xms40M
-Xmx256M

So you can change the default value to:

-vmargs
-Xms256M
-Xmx512M

Of course, you can also do this by changing the size of the heap to 256-512.

C:\eclipse\eclipse.exe -vm "C:\Program Files\Java\jdk1.5.0_08\ bin\javaw.exe" -vmargs -Xms256M -Xmx512M

3. Other start-up parameters. If you have a dual-core CPU, you might be able to try this parameter:

-XX:+UseParallelGC

Allows the GC to execute faster. (only new parameters added to the GC in JDK 5)

(RPM) Introduction to eclipse startup parameters (such as when adding plug-ins, if not displayed, start with Eclipse-clean)