After referring to some materials, I have summarized some commonly used command arguments at startup. If there are any errors, I hope you can point out them.
-arch [processor architecture]
Description: Specifies the type of processor to use
Example: Eclipse – arch x86 or eclipse – arch SPARC
Description: specify the application to run. The ID is the plug-in ID of the extension org.eclipse.core.applications extension point plus the extension ID
For example, if a plug-in ID is edu.sdu.app and the extension ID is myapp, eclipse – Application edu.sdu.app.myapp will execute your extension application
Description: clears the contents of the plug-in cache
For example: Eclipse – clean, sometimes the plug-in is not displayed because eclipse caches the plug-in to speed up the startup process. If this parameter is specified, the cache will be emptied and loaded from scratch
-configuration [cofigfile location]
Description: Specifies the location of the configuration file. When starting, use the configuration file config.ini in this directory to start
Example: Eclipse – configuration D: / eclipse / configuration
-data [workspace location]
Description: Specifies the workspace location at startup
For example, if the workspace location is set to D: / myworkspace, eclipse – data D: / myworkspace
-debug [option file]
Description: start 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: start eclipse in the development state, which will add all specified paths as the classpath of each plug-in
For example, eclipse – Dev bin will load all classes generated in the bin directory into the classpath, which is very useful when developing plug-ins
Description: Specifies that the flash screen is not displayed at startup
Example: Eclipse – noslash
-vm [jre path]
Description: Specifies the Java virtual machine to use at startup
For example, if you want to use your own Java virtual machine, eclipse – VMD: / j2sdk1.4.2_ 04 / JRE / bin / java.exe. Another advantage is that you can open a console and display console information. Of course, if you use eclipse – VM D: / j2sdk1.4.2_ 04 / JRE / bin / javaw.exe will no longer display the console
-vmargs [Java VM arguments]
Description: Specifies the Java virtual machine parameters to use at startup
For example, to specify the memory capacity to use, eclipse – vmargs “- xms256m – xmx1024m”
Note: this parameter must be placed at the end of all parameter variables
If you think your eclipse starts slowly (for example, more than 20 seconds), maybe you need to adjust your eclipse startup parameters. Here are some “tips”:
1. Check the JVM settings for starting eclipse. In help \ about eclipse SDK \ configuration detail, you can see the JVM that starts eclipse. The JVM and the installed JDK you set in eclipse are two things. If the JVM that starts eclipse is still JDK 1.4, it’s better to change to JDK 5, because the performance of JDK 5 is better 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 configuration file eclipse.ini in 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 heap size to 256 – 512.
C:\eclipse\eclipse.exe -vm "C:\Program Files\Java\jdk1.5.0_08\ bin\javaw.exe" -vmargs -Xms256M -Xmx512M
3. Other startup parameters. If you have a dual core CPU, maybe you can try this parameter:
GC can execute faster（ Only the newly added parameters for GC in JDK 5)
There are several ways to start Eclipse:
0. Copy JRE to eclipse directory.
1. Specify the parameters directly after the command line: Eclipse – VM… This has been tried, and you can.
2. Add: – VM in eclipse.ini file This place -vm needs a new line.
3. You can also search javaw.exe in the path environment variable.
It is said that the designation of javaw.exe virtual machine is better to point to bin \ javaw.exe under JRE directory. It is said that it will be faster.