What are the best JVM settings for Eclipse

Question

What are the best JVM settings you have found for running Eclipse

User · Answer

Here s my own setting for my Eclipse running on i7 2630M 16GB RAM laptop  this setting has been using for a week  without a single crashing  and Eclipse 3 7 is running smoothly   -startup plugins org eclipse equinox launcher 1 2 0 v20110502 jar --launcher library plugins org eclipse equinox launcher win32 win32 x86 64 1 1 100 v20110502 -product org eclipse epp package jee product --launcher defaultAction openFile --launcher XXMaxPermSize 256M -showsplash org eclipse platform --launcher XXMaxPermSize 256m --launcher defaultAction openFile -vmargs -Dosgi requiredJavaVersion 1 5 -Xms1024m -Xmx4096m  -XX MaxPermSize 256m   Calculations  For Win 7 x64   Xms   Physical Memory   16  Xmx   Physical Memory   4  MaxPermSize   Same as default value  which is 256m

User · Answer

If you are using Linux   Sun JDK JRE 32bits  change the  -vm  to   -vm   your jdk folder  jre lib i386 client libjvm so   If you are using Linux   Sun JDK JRE 64bits  change the  -vm  to   -vm  your jdk folder  jre lib amd64 server libjvm so   That s working fine for me on Ubuntu 8 10 and 9 04

User · Answer

Eclipse Indigo 3 7 2 settings  64 bit linux   Settings for Sun Oracle java version  1 6 0 31  and Eclipse 3 7 running on x86-64 Linux   -nosplash -vmargs -Xincgc -Xss500k -Dosgi requiredJavaVersion 1 6 -Xms64m -Xmx200m -XX NewSize 8m -XX PermSize 80m -XX MaxPermSize 150m -XX MaxPermHeapExpansion 10m -XX  UseConcMarkSweepGC -XX CMSInitiatingOccupancyFraction 70 -XX  UseCMSInitiatingOccupancyOnly -XX  UseParNewGC -XX  CMSConcurrentMTEnabled -XX ConcGCThreads 2 -XX ParallelGCThreads 2 -XX  CMSIncrementalPacing -XX CMSIncrementalDutyCycleMin 0 -XX CMSIncrementalDutyCycle 5 -XX GCTimeRatio 49 -XX MaxGCPauseMillis 20 -XX GCPauseIntervalMillis 1000 -XX  UseCMSCompactAtFullCollection -XX  CMSClassUnloadingEnabled -XX  DoEscapeAnalysis -XX  UseCompressedOops -XX  AggressiveOpts -XX  ExplicitGCInvokesConcurrentAndUnloadsClasses   Note that this uses only 200 MB for the heap and 150 MB for the non-heap  If you re using huge plugins  you might want to increase both the  -Xmx200m  and  -XX MaxPermSize 150m  limits   The primary optimization target for these flags has been to minimize latency in all cases and as a secondary optimization target minimize the memory usage

User · Answer

Eclipse Ganymede 3 4 2 settings    For more recent settings  see Eclipse Galileo 3 5 settings above       JDK  The best JVM setting always  in my opinion  includes the latest JDK you can find  so for now  jdk1 6 0 b07 up to b16  except b14 and b15   eclipse ini  Even with those pretty low memory settings  I can run large java projects  along with a web server  on my old  2002  desktop with 2Go RAM   -showlocation -showsplash org eclipse platform --launcher XXMaxPermSize 256M -framework plugins org eclipse osgi 3 4 2 R34x v20080826-1230 jar -vm jdk1 6 0 10 jre bin client jvm dll -vmargs -Dosgi requiredJavaVersion 1 5 -Xms128m -Xmx384m -Xss2m -XX PermSize 128m -XX MaxPermSize 128m -XX MaxGCPauseMillis 10 -XX MaxHeapFreeRatio 70 -XX  UseConcMarkSweepGC -XX  CMSIncrementalMode -XX  CMSIncrementalPacing -XX CompileThreshold 5 -Dcom sun management jmxremote   See GKelly s SO answer and Piotr Gabryanczyk s blog entry for more details about the new options   Monitoring  You can also consider launching   C   jdk1 6 0 0x path  bin jconsole exe   As said in a previous question about memory consumption

User · Answer

If you are using Linux   Sun JDK JRE 32bits  change the  -vm  to   -vm   your jdk folder  jre lib i386 client libjvm so   If you are using Linux   Sun JDK JRE 64bits  change the  -vm  to   -vm  your jdk folder  jre lib amd64 server libjvm so   That s working fine for me on Ubuntu 8 10 and 9 04

User · Answer

-vm C  Program Files Java jdk1 6 0 07 jre bin client jvm dll  To specify which java version you are using  and use the dll instead of launching a javaw process

User · Answer

Eclipse Galileo 3 5 and 3 5 1 settings  Currently  November 2009   I am testing with jdk6 update 17 the following configuration set of options  with Galileo -- eclipse 3 5 x  see below for 3 4 or above for Helios 3 6 x    of course  adapt the relative paths present in this eclipse ini to the correct paths for your setup   Note  for eclipse3 5  replace startup and launcher library lines by   -startup plugins org eclipse equinox launcher 1 0 200 v20090520 jar --launcher library plugins org eclipse equinox launcher win32 win32 x86 1 0 200 v20090519   eclipse ini 3 5 1  -data       workspace -showlocation -showsplash org eclipse platform --launcher XXMaxPermSize 384m -startup plugins org eclipse equinox launcher 1 0 201 R35x v20090715 jar --launcher library plugins org eclipse equinox launcher win32 win32 x86 1 0 200 v20090519 -vm             program files Java jdk1 6 0 17 jre bin client jvm dll -vmargs -Dosgi requiredJavaVersion 1 5 -Xms128m -Xmx384m -Xss4m -XX PermSize 128m -XX MaxPermSize 384m -XX CompileThreshold 5 -XX MaxGCPauseMillis 10 -XX MaxHeapFreeRatio 70 -XX  UseConcMarkSweepGC -XX  CMSIncrementalMode -XX  CMSIncrementalPacing -Dcom sun management jmxremote -Dorg eclipse equinox p2 reconciler dropins directory C  jv eclipse mydropins   See also my original answer above for more information   Changes  from July 2009    refers to the launcher and not the framework shared plugins  org eclipse equinox p2 reconciler dropins directory option  Galileo supports fully relative paths for workspace or VM  avoid having to modify those from one eclipse installation to another  if  of course  your JVM and workspace stay the same  Before  those relative paths kept being rewritten into absolute ones when eclipse launched itself    You also can copy the JRE directory of a Java JDK installation inside your eclipse directory   Caveats  There was a bug with ignored breakpoints actually related to the JDK  Do use JDK6u16 or more recent for launching eclipse  You can then define as many JDKs you want to compile within eclipse  it is not because you launch an eclipse with JDK6 that you will have to compile with that same JDK    Max  Note the usage of   --launcher XXMaxPermSize 384m -vmargs -XX MaxPermSize 128m   As documented in the Eclipse Wiki       Eclipse 3 3 supports a new argument to the launcher  --launcher XXMaxPermSize    If the VM being used is a Sun VM and there is not already a -XX MaxPermSize  VM argument  then the launcher will automatically add -XX MaxPermSize 256m to the list of VM arguments being used    The 3 3 launcher is only capable of identifying Sun VMs on Windows    As detailed in this entry      Not all vms accept the -XX MaxPermSize argument which is why it is passed in this manner  There may  or may not  exist problems with identifying sun vms    Note  Eclipse 3 3 1 has a bug where the launcher cannot detect a Sun VM  and therefore does not use the correct PermGen size  It seems this may have been a known bug on Mac OS X for 3 3 0 as well    If you are using either of these platform combination  add the -XX flag to the eclipse ini as described above       Notes          the  384m  line translates to the   384m  part of the VM argument  if the VM is case sensitive on the  m   then the so is this argument      the  --launcher   prefix  this specifies that the argument is consumed by the launcher itself and was added to launcher specific arguments to avoid name collisions with application arguments   Other examples are --launcher library  --launcher suppressErrors          The -vmargs -XX MaxPermSize 384m part is the argument passed directly to the VM  bypassing the launcher entirely and no check on the VM vendor is used

User · Answer

-showlocation  To make it easier to have eclipse running twice  and know which workspace you re dealing with  Eclipse 3 6 adds a preferences option to specify what to show for the Workspace name  shown in window title  which works much better than -showlocation for three reasons    You do not need to restart eclipse for it to take affect  You can chose a short code  It appears first  before the perspective and application name

User · Answer

Here s what I use  though I have them in the shortcut instead of the settings file    eclipse exe -showlocation -vm  C  Java jdk1 6 0 07 bin javaw exe  -vmargs -Xms256M -Xmx768M -XX  UseParallelGC -XX MaxPermSize 128M

User · Answer

It is that time of year again   eclipse ini take 3  the settings strike back     Eclipse Helios 3 6 and 3 6 x settings  alt text http   www eclipse org home promotions friends-helios helios png  After settings for Eclipse Ganymede 3 4 x and Eclipse Galileo 3 5 x  here is an in-depth look at an  optimized  eclipse ini settings file for Eclipse Helios 3 6 x    based on runtime options   and using the Sun-Oracle JVM 1 6u21 b7  released July  27th  some some Sun proprietary options may be involved      by  optimized   I mean able to run a full-fledge Eclipse on our crappy workstation at work  some old P4 from 2002 with 2Go RAM and XPSp3  But I have also tested those same settings on Windows7   Eclipse ini     WARNING  for non-windows platform  use the Sun proprietary option -XX MaxPermSize instead of the Eclipse proprietary option --launcher XXMaxPermSize  That is  Unless you are using the latest jdk6u21 build 7   See the Oracle section below   -data       workspace -showlocation -showsplash org eclipse platform --launcher defaultAction openFile -vm C  Prog Java jdk1 6 0 21 jre bin server jvm dll -vmargs -Dosgi requiredJavaVersion 1 6 -Declipse p2 unsignedPolicy allow -Xms128m -Xmx384m -Xss4m -XX PermSize 128m -XX MaxPermSize 384m -XX CompileThreshold 5 -XX MaxGCPauseMillis 10 -XX MaxHeapFreeRatio 70 -XX  CMSIncrementalPacing -XX  UnlockExperimentalVMOptions -XX  UseG1GC -XX  UseFastAccessorMethods -Dcom sun management jmxremote -Dorg eclipse equinox p2 reconciler dropins directory C  Prog Java eclipse addons   Note  Adapt the p2 reconciler dropins directory to an external directory of your choice  See this SO answer  The idea is to be able to drop new plugins in a directory independently from any Eclipse installation   The following sections detail what are in this eclipse ini file       The dreaded Oracle JVM 1 6u21  pre build 7  and Eclipse crashes  Andrew Niefer did alert me to this situation  and wrote a blog post  about a non-standard vm argument  -XX MaxPermSize  and can cause vms from other vendors to not start at all  But the eclipse version of that option  --launcher XXMaxPermSize  is not working with the new JDK  6u21  unless you are using the 6u21 build 7  see below    The final solution is on the Eclipse Wiki  and for Helios on Windows with 6u21 pre build 7 only    downloading the fixed eclipse 1308 dll  July 16th  2010  and place it into     eclipse home  plugins org eclipse equinox launcher win32 win32 x86 1 1 0 v20100503   That s it  No setting to tweak here  again  only for Helios on Windows with a 6u21 pre build 7   For non-Windows platform  you need to revert to the Sun proprietary option -XX MaxPermSize   The issue is based one a regression  JVM identification fails due to Oracle rebranding in java exe  and triggered bug 319514 on Eclipse  Andrew took care of  Bug 320005 -   launcher  --launcher XXMaxPermSize  isSunVM should return true for Oracle  but that will be only for Helios 3 6 1  Francis Upton  another Eclipse committer  reflects on the all situation   Update u21b7  July  27th  Oracle have regressed the change for the next Java 6 release and won t implement it again until JDK 7  If you use jdk6u21 build 7  you can revert to the --launcher XXMaxPermSize  eclipse option  instead of -XX MaxPermSize  the non-standard option   The auto-detection happening in the C launcher shim eclipse exe will still look for the  Sun Microsystems  string  but with 6u21b7  it will now work - again   For now  I still keep the -XX MaxPermSize version  because I have no idea when everybody will launch  eclipse the right JDK      Implicit  -startup  and  --launcher library   Contrary to the previous settings  the exact path for those modules is not set anymore  which is convenient since it can vary between different Eclipse 3 6 x releases    startup  If not specified  the executable will look in the plugins directory for the org eclipse equinox launcher bundle with the highest version  launcher library  If not specified  the executable looks in the plugins directory for the appropriate org eclipse equinox launcher  platform  fragment with the highest version and uses the shared library named eclipse   inside      Use JDK6  The JDK6 is now explicitly required to launch Eclipse   -Dosgi requiredJavaVersion   1 6   This SO question reports a positive incidence for development on Mac OS      UnlockExperimentalVMOptions  The following options are part of some of the experimental options of the Sun JVM   -XX  UnlockExperimentalVMOptions -XX  UseG1GC -XX  UseFastAccessorMethods   They have been reported in this blog post to potentially speed up Eclipse  See all the JVM options here and also in the official Java Hotspot options page  Note  the detailed list of those options reports that UseFastAccessorMethods might be active by default     See also  Update your JVM       As a reminder  G1 is the new garbage collector in preparation for the JDK 7  but already used in the version 6 release from u17      Opening files in Eclipse from the command line  See the blog post from Andrew Niefer reporting this new option   --launcher defaultAction openFile      This tells the launcher that if it is called with a command line that only contains arguments that don t start with  -   then those arguments should be treated as if they followed  --launcher openFile     eclipse myFile txt      This is the kind of command line the launcher will receive on windows when you double click a file that is associated with eclipse  or you select files and choose  Open With  or  Send To  Eclipse       Relative paths will be resolved first against the current working directory  and second against the eclipse program directory    See bug 301033 for reference  Originally bug 4922  October 2001  fixed 9 years later      p2 and the Unsigned Dialog Prompt  If you are tired of this dialog box during the installation of your many plugins       add in your eclipse ini   -Declipse p2 unsignedPolicy allow   See this blog post from Chris Aniszczy  and the bug report 235526       I do want to say that security research supports the fact that less prompts are better    People ignore things that pop up in the flow of something they want to get done       For 3 6  we should not pop up warnings in the middle of the flow - no matter how much we simplify  people will just ignore them    Instead  we should collect all the problems  do not install those bundles with problems  and instead bring the user back to a point in the workflow where they can fixup - add trust  configure security policy more loosely  etc  This is called  safe staging     ---------- http   www eclipse org home categories images wiki gif alt text http   www eclipse org home categories images wiki gif alt text http   www eclipse org home categories images wiki gif   Additional options  Those options are not directly in the eclipse ini above  but can come in handy if needed     The  user home  issue on Windows7  When eclipse starts  it will read its keystore file  where passwords are kept   a file located in user home  If for some reason that user home doesn t resolve itself properly to a full-fledge path  Eclipse won t start  Initially raised in this SO question  if you experience this  you need to redefine the keystore file to an explicit path  no more user home to resolve at the start   Add in your eclipse ini   -eclipse keyring  C  eclipse keyring txt   This has been tracked by bug 300577  it has been solve in this other SO question     Debug mode  Wait  there s more than one setting file in Eclipse  if you add to your eclipse ini the option   -debug     you enable the debug mode and Eclipse will look for another setting file  a  options file where you can specify some OSGI options  And that is great when you are adding new plugins through the dropins folder  Add in your  options file the following settings  as described in this blog post  Dropins diagnosis    org eclipse equinox p2 core debug true org eclipse equinox p2 core reconciler true      P2 will inform you what bundles were found in dropins  folder  what request was generated  and what is the plan of installation  Maybe it is not detailed explanation of what actually happened  and what went wrong  but it should give you strong information about where to start          was your bundle in the plan     Was it installation problem  P2 fault     or maybe it is just not optimal to include your feature       That comes from Bug 264924 -  reconciler  No diagnosis of dropins problems  which finally solves the following issue like   Unzip eclipse-SDK-3 5M5-win32 zip to      eclipse Unzip mdt-ocl-SDK-1 3 0M5 zip to      eclipse dropins mdt-ocl-SDK-1 3 0M5      This is a problematic configuration since OCL depends on EMF which is missing    3 5M5 provides no diagnosis of this problem       Start eclipse    No obvious problems  Nothing in Error Log          Help   About   Plugin details shows org eclipse ocl doc  but not org eclipse ocl    Help   About   Configuration details has no  diagnostic  mention of   org eclipse ocl    Help   Installation   Information Installed Software has no mention of org eclipse ocl          Where are the nice error markers      Manifest Classpath  See this blog post         In Galileo  aka Eclipse 3 5   JDT started resolving manifest classpath in libraries added to project   s build path  This worked whether the library was added to project   s build path directly or via a classpath container  such as the user library facility provided by JDT or one implemented by a third party     In Helios  this behavior was changed to exclude classpath containers from manifest classpath resolution        That means some of your projects might no longer compile in Helios  If you want to revert to Galileo behavior  add   -DresolveReferencedLibrariesForContainers true   See bug 305037  bug 313965 and bug 313890 for references     IPV4 stack  This SO question mentions a potential fix when not accessing to plugin update sites   -Djava net preferIPv4Stack true   Mentioned here just in case it could help in your configuration     JVM1 7x64 potential optimizations  This article reports      For the record  the very fastest options I have found so far for my bench test with the 1 7 x64 JVM n Windows are     -Xincgc  -XX -DontCompileHugeMethods  -XX MaxInlineSize 1024   -XX FreqInlineSize 1024       But I am still working on it

User · Answer

You can also try running with JRockit  It s a JVM optimized for servers  but many long running client applications  like IDE s  run very well on JRockit  Eclipse is no exception  JRockit doesn t have a perm-space so you don t need to configure it    It s possible set a pause time target ms  to avoid long gc pauses stalling the UI    -showsplash org eclipse platform -vm  C  jrmc-3 1 2-1 6 0 bin javaw exe  -vmargs -XgcPrio deterministic -XpauseTarget 20   I usually don t bother setting -Xmx and -Xms and let JRockit grow the heap as it sees necessary  If you launch your Eclipse application with JRockit you can also monitor  profile and find memory leaks in your application using the JRockit Mission Control tools suite  You download the plugins from this update site  Note  only works for Eclipse 3 3 and Eclipse 3 4

User · Answer

-startup          plugins org eclipse equinox launcher 1 2 0 v20110502 jar --launcher library          plugins org eclipse equinox launcher cocoa macosx 1 1 100 v20110502 -showsplash org eclipse platform --launcher XXMaxPermSize 256m --launcher defaultAction openFile -vmargs -Xms128m -Xmx512m -XX MaxPermSize 256m -Xdock icon    Resources Eclipse icns -XstartOnFirstThread -Dorg eclipse swt internal carbon smallFonts -Dcom sun management jmxremote -Declipse p2 unsignedPolicy allow   And these setting have worked like a charm for me  I am running OS X10 6   Eclipse 3 7 Indigo   JDK1 6 0 24

User · Answer

If you re going with jdk6 update 14  I d suggest using using the G1 garbage collector which seems to help performance   To do so  remove these settings   -XX  UseConcMarkSweepGC -XX  CMSIncrementalMode -XX  CMSIncrementalPacing  and replace them with these   -XX  UnlockExperimentalVMOptions -XX  UseG1GC

User · Answer

My own settings  Java 1 7  modify for 1 6    -vm C  Program Files  x86  Java jdk1 7 0 bin -startup plugins org eclipse equinox launcher 1 1 0 v20100507 jar --launcher library plugins org eclipse equinox launcher win32 win32 x86 1 1 100 v20100628 -showsplash org eclipse platform --launcher XXMaxPermSize 256m --launcher defaultAction openFile -vmargs -server -Dosgi requiredJavaVersion 1 7 -Xmn100m -Xss1m -XgcPrio deterministic -XpauseTarget 20 -XX PermSize 400M -XX MaxPermSize 500M -XX CompileThreshold 10 -XX MaxGCPauseMillis 10 -XX MaxHeapFreeRatio 70 -XX  UnlockExperimentalVMOptions -XX  DoEscapeAnalysis -XX  UseG1GC -XX  UseFastAccessorMethods -XX  AggressiveOpts -Xms512m -Xmx512m

User · Answer

If youre like me and had problems with the current Oracle release of 1 6 then you might want to update your JDK or set -XX MaxPermSize  More information is available here  http   java dzone com articles latest-java-update-fixes

User · Answer

Eclipse likes lots of RAM   Use at least -Xmx512M   More if available

User · Answer

XX  UseParallelGC that s the most awesome option ever

[eclipse] What are the best JVM settings for Eclipse?

Examples related to eclipse

Examples related to jvm