Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Performance Settings - eclipse.ini
Also see Command Line Switches.
The following changes have to be made to the eclipse.ini file.
In your Applications folder go to Eclipse.app >> right-click >> Show Package Contents Then navigate to /Contents/MacOS
Note: A single VM argument ("-vmargs") specified in Info.plist will cause all other VM arguments in the eclipse.ini to be ignored.
You should locate the file in you Eclipse directory i.e. C:\Program Files\eclipse
You can use a plain text editor to modify the files.
Add the following variables to the ini file:
-vm C:\Program Files\Java\jre1.6.0_02\bin\javaw.exe -vmargs -Xms512m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=128m -Xverify:none
- The first two lines explicitly set which JVM is used.
- The third line specifies that VM arguments are coming next.
- Lines four through seven change how the memory is managed.
- The last line should reduce your startup time. This parameter turns off bytecode verification. I'm not a Java expert (so please someone jump in if I am wrong) but you should only set this if you know your plugins work fine. In essence this checks for the Java language rules for safety and the code may not have been produced by a known-to-be trustworthy Java compiler meaning that you could end up crashing Eclipse as your plugin might violate access restrictions etc.
- Turbo-charging Eclipse (Mike Henke)