Blogging Roller

Dave Johnson on social software, open source and Java

GC settings to improve Eclipse performance.

eclipse.exe -vmargs -Xverify:none -XX:+UseParallelGC -XX:PermSize=20M  
-XX:MaxNewSize=32M -XX:NewSize=32M -Xmx96m -Xms96m
Sosume applies some new GC configuration settings, written about in JavaWorld and recommended for Netbeans to improve Eclipse performance in his post: Improving Eclipse performance by using vm arguments. I'm trying these settings myself now, but with -Xmx256m.
Comments:

I tried this out, but the memory settings don't seem to have anything to do with startup time. <B>18</B> seconds - "eclipse.exe" <B>13</B> seconds - "eclipse.exe -vmargs -Xverify:none" <B>12</B> seconds - "eclipse.exe -vmargs -Xverify:none -XX:+UseParallelGC -XX:PermSize=20M -XX:MaxNewSize=32M -XX:NewSize=32M -Xmx96m -Xms96m" It's only the Xverify:none parameter which has a noticeable effect on reducing startup time. On the java website I found that this parameter turns off bytecode verification (http://developer.java.sun.com/developer/onlineTraining/Security/Fundamentals/Security.html), although the default is supposedly "only verify classes loaded over the network". In addition, when I just use the verify:none flag Eclipse (according to Windows) uses 35 megabytes of memory. When I specificy memory usage, 127 megabytes of memory.

Posted by Paul Rivers on March 13, 2003 at 08:55 PM EST #

I would post this on Ultraplex's blog, but he doesn't seem to have comments. I tried the same thing and it didn't work on jdk1.4.0. I upgraded to jdk1.4.1 - and then it worked.

Posted by Paul Rivers on March 15, 2003 at 08:58 PM EST #

Post a Comment:
  • HTML Syntax: Allowed