On a Mac, the following procedure allows the JVM settings to be changed:
The JVM options that make the biggest difference are the ones that specify how much memory Eclipse can use.
I also tell the JVM not to verify bytecode using the -Xverify switch
According to the NetBeans performance tuning tips, changing the garbage collection policies can also make a difference. I’m not sure that these make much of a difference, but I’m running with them at the moment to see if there is any difference.
- Find Eclipse in the Finder. Right click on Eclipse and choose "Show Package Contents"
- Browse to the Contents | MacOS directory and edit the eclipse.ini file
- In this file add JVM options, one per line.
The JVM options that make the biggest difference are the ones that specify how much memory Eclipse can use.
1 2 3 4 | -Xms512m -Xmx512m -XX:PermSize=256m -XX:MaxPermSize=256m |
I also tell the JVM not to verify bytecode using the -Xverify switch
1 | -Xverify:none |
According to the NetBeans performance tuning tips, changing the garbage collection policies can also make a difference. I’m not sure that these make much of a difference, but I’m running with them at the moment to see if there is any difference.
1 2 3 | -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled |
See the entire post.
