Accepted answer

the three most influential factors for eclipse speed are:

  • using the latest version of eclipse (2020-06 as on 26 june 2020)
    note that david balažic's comment (july 2014) contradicts that criteria which was working six years ago:

the "same" workspace in indigo (3.7.2) sr2 loads in 4 seconds, in kepler sr2 (4.3.2) in 7 seconds and in luna (4.4.0) in 10 seconds. all are java ee bundles. newer versions have more bundled plugins, but still the trend is obvious. (by "same" workspace i mean: same (additionally installed) plugins used, same projects checked out from version control).

  • launching it with the latest jdk (java 14 at the time of writing, which does not prevent you to compile in your eclipse project with any other jdk you want: 1.4.2, 1.5, 1.6 older...)

      -vm jdk1.6.0_10\jre\bin\client\jvm.dll
  • configuring the eclipse.ini (see this question for a complete eclipse.ini)


the xmx argument is the amount of memory eclipse will get (in simple terms). with -xmx4g, it gets 4 gb of ram, etc.


  1. referring to the jvm.dll has advantages:
  • splash screen coming up sooner.
  • eclipse.exe in the process list instead of java.exe.
  • firewalls: eclipse wants access to the internet instead of java.
  • window management branding issues, especially on windows and mac.

dec. 2020, udo conforms in the comments

from version 4.8 (photon) an up there was a steady speed gain after each version.
the main platform was optimized every release to load faster, enable more features for the dark theme and to add more features for newer java versions for the java development tools.
especially with-in the last 3 versions the startup time was increased a lot. there should be a significant increase in start-up time with the newest version of eclipse 2020-12.

in my experience it started a lot faster with each new version.
but: there are still plug-ins which do not follow the new way of using the eclipse api and are therefore still slow to start.
since the change to java 11 as the minimum runtime version starting from eclipse version 2020-09 at least the core system uses the newer features of the jvm. it is up to the providers of the other plug-ins to upgrade to newer apis and to use the full power of modern cpus (e.g. concurrent programming model).


there could be several things that could delay the start and exit of eclipse. one of them is like familiar to what we have a lookalike in windows. disabling the windows animations and disabling startup activities speeds up windows to certain extent

similar to what in eclipse we can have the same thing windows-> general -> preferences -> appearance -> turning off some decorative options. this would give a little boost but may not have much impact.

in my opinion, the projects in the work space you might have created should be limited to certain extent or rather creating a new work space if projects are more. for instance, when you try to run a single project on server it takes less time as compared to running several projects on the same server


for windows users:

if you go to task manager, choose the eclipse application, and click on the little arrow next to it, you will usually just see one sub-process appear below "eclipse.exe". however, in my case, if you have multiple instances of "java platform se binary", then end all of them. for some reason, i had three of these running in the background, even though i wasn't currently running any projects. nevertheless, this will boost performance back to the way it likely was when you first installed eclipse on your computer.

if you can no longer run a project after the change, then try relaunching eclipse.


do you have a huge ram? create a ramdisk and place there your

  • jdk
  • jvm
  • eclipse
  • workspace

make sure you persist your changes back to your hdd or commit them to vcs to avoid data-loose on power-off.


if you're not bound to eclipse for reasons like work, some plug-in\functionality you need that's only available through eclipse and so forth; then one a possible strategy is to get rid of eclipse altogether. this will speed up things tremendously.

you could switch to any other ide or development environment that does what you need. one example would be netbeans. some proposed speed-ups also apply to netbeans, or any other ide for that matter.

one example that applies directly to linux, is to move as much as possible to a tmpfs mount. for java development in netbeans, i've moved the java documentation and source to a tmpfs mount which resulted in an enormous performance boost.

likewise, during c++ development i'll make sure the whole source tree is in my tmpfs mount if possible. although i haven't extensively benchmarked build performance, a few tests on a reasonably sized codebase (few hundred source files + headers) resulted in a >50% decrease in compilation time.

do keep in mind that your data will not persist during a power loss when using this method. to combat this, one could create a script that rsyncs the tmpfs mount to some backup-directory and add that script as a cronjob that runs every minute.


increase your ram to more than 8 gb and disable autobuild project. this worked for me.


i have tried many permutations by increasing heapspace and changing the garbage collector settings to speed up eclipse.

but for my local development, in my humble opinion, i have seen that disabling the jvm garbage collector works best for me.

mylyn autocomplete feature works with no issue and the (not responding) part has been significantly minimzed.

below is a snapshot of my eclipse.ini file.


i have tried using jdk 6 and jdk 8, and in both cases, noticed a significant speedup.


this article how to quickly make eclipse faster is very useful. i tried some tips and it's true; it made my eclipse run faster.


the problem could be java cache, or java temporary files.

open control panel on windows, find java panel click settings on general tab, delete temprorary files, and set amount of disk space for storing temporary files od 10000mb or less. restart eclipse. restore all validators and you will see that speed your ide eclipse is ok.


there is once more solution delete all files from this two folders

.metadata.plugins\org.eclipse.core.resources.history .metadata.plugins\org.eclipse.jdt.core

this help for the first momment. but it still stay slow


i had similar slowdown and this fix applies only if you are using the c/c++ variant of the eclipse. for c/c++ you may want to disable the indexer which is famous for cpu hog. it is the equivalent of vs intellisense. to disable cdt indexer go to window->preferences, underc/c++ tab select indexer and uncheck the enable indexer.


we use git as cvs and gradle as build tool.


in my case one specific project with > 20'000 files froze using hierarchical view when navigating a directory with a lot of files.


  1. create new eclipse workspace
  2. freshly clone the project into the eclipse workspace
  3. import project into eclipse (in our case using gradle import)


close the outline view to speed up switching between editors.
each time you switch to a different tab or open a file, the outline view has to update, which on my machine took about 1 second every time. it's just 1 second, but if you change tabs very often, like me, it will save you a headache.


a few steps i follow, if eclipse is working slow:

  1. any unused plugins installed in eclipse, should uninstall them. -- few plugins makes a lot much weight to eclipse.
  2. open current working project and close the remaining project. if there is any any dependency among them, just open while running. if all are maven projects, then with miner local change in pom files, you can make them individual projects also. if you are working on independent projects, then always work on any one project in a workspace. don't keep multiple projects in single workspace.

  3. change the type filters. it facilitates to specify particular packages to refer always.

  4. as per my experience, don't change memory jvm parameters. it causes a lot of unknown issues except when you have sound knowledge of jvm parameters.

  5. un-check auto build always. particulary, maven project's auto build is useless.

  6. close all the files opened, just open current working files.

  7. use go into work sets. instead of complete workbench.

  8. most of the components of your application you can implement and test in standalone also. learn how to run in standalone without need of server deploy, this makes your work simple and fast. -- recently, i worked on hibernate entities for my project, two days, i did on server. i.e. i changed in entities and again build and deployed on the server, it killing it all my time. so, then i created a simple jpa standalone application, and i completed my work very fast.


the only real way to hasten eclipse with the standard plug-ins is to give it more memory and in some cases access to a faster storage space / defragmented hard drive.

beyond that there is not much you can do performance-wise: most standard plug-ins do not have a continuous runtime cost, even mylyn is relatively fast.

upgrading to the latest jvm supported on your machine may help as well.

some people downgrade to older eclipse versions to get better performance. it may also make sense to use eclipse classic instead of the official releases.


try these. there are two ways.

first procedure

refer this article.

second procedure.

execute the command in the terminal.


to get better performance and fast response for ubuntu.

ramdisk is part of system memory. ubuntu by default uses a half of physical memory (ram) as ramdisk, and it is mounted onto


, it can be used just like normal disk space (create files and folders and manipulate them with better performance rather if they were stored on the hard disk). if ramdisk uses more than a half of ram, data will be moved into the swap space. if ramdisk uses less, the remaining can still do what ram’s doing.

set upper limit of ramdisk

as is said above, ramdisk by default can use a half of ram. if you want to change the upper limit, follow the steps below:

  1. edit /etc/fstab by your favourate editor:

    gksudo gedit /etc/fstab

  2. find this line and change to make it looks like this(add this line if not exist, and change 512m to what you like.):

    tmpfs /dev/shm tmpfs defaults,size=512m 0 0

  3. reboot or re-mount


mount /tmp onto ramdisk

to make it easy to use, you can mount a directory into


by following commands:

mkdir /dev/shm/tmp

chmod 1777 /dev/shm/tmp

mount --bind /dev/shm/tmp /tmp


well, if you are developing a gwt application using eclipse, then this is the way:

out of memory error in eclipse

also remember to add the same vm arguments to the hosted mode configuration.


if you use maven and ivy do check out their consoles in case they are hogging processing during builds. i use ivy and on top of that i have certain jar files (internal) changing with same version, so it has to workout all the time to fetch them.

if you have defined you project on a network drive then you will also experience lag during build/read/write type of processes.

  • disable/uninstall plugins you don't need.

  • close perpective that you don't need

  • close unused database connections


in special cases, bad performance can be due to corrupt h2 or nwire databases. read five tips for speeding up eclipse pdt and nwire for more information.

where i work, we are dependent on a vm to run debian. i have installed another eclipse version on the vm for testing purpouses, but this sometimes creates conflicts if i have the other eclipse version running. there is a shared folder which both of the eclipse versions shares. i accidentally left the debian eclipse installation running in the background once and that gave me corrupt database files.


on windows 8. open control panel. find windows defender. go to settings exclude all folders where is your spring/eclipse and workspace


apart from configuring eclipse.ini for memory usage. i have configured by "start up & shutdown options". my eclipse is blazing fast now.

enter image description here


try this too, it will improve the performance:

cleaning up indexes - {workspace path}.metadata.plugins\org.eclipse.jdt.core cleaning up history - {workspace path}.metadata.plugins\org.eclipse.core.resources.history

cleaning the above folders will not impact the project files.


i've disabled all unused options in windows > preferences > general and it has a huge positive impact on performance, eclipse is still slow when switching tabs, i don't want to increase memory, but it's a lot faster when scrolling. thx for the tips.


                       **tips for making eclipse ide faster**

eclipse will run faster when working with small projects. but when you have to work with large project, you will get irritated with its speed. even with a huge ram you will not be happy with its speed.below steps will help eclipse to increase its speed

  1. remove unwanted activation of some of the plugins at start-up by going to windows–>preference–>general–>startup and shutdown also make sure you don’t use those plugins in any of your views

  2. disabling label decorations which is of less use for you, will also help you to gain some performance . go to windows–>preference–>general–>appearance–>label -> decorations

  3. close unwanted projects and use working set option to move from one group of project to another smoothly.

  4. configure eclipse.ini which will be available in the eclipse installed location.

   configuring eclipse.ini should be based on your ram

also have a look at for more options to configure eclipse.ini.

  1. do not keep lot of tabs opened in the editor. better to have around 20 tabs . regularly close the unused tabs. to open resource we can always use ctrl+shift+r and ctrl+shift+t (java resource) instead of opening lot of tabs i experienced a considerable improvement in performance when limiting the number of open tabs (in the past i frequently had 30+ tabs open). you can let eclipse handle this for you automatically: window->preferences->editors-> close editors automatically 8 open tabs is the amount before the >> sign appears, so i set 14 as my default value. when opening more tabs, the ones the least recently accessed will be closed. when all editors are dirty or pinned. if it has unsaved modifications you can prompt to save & reuse (tab will be closed, a new one will be opened in its place). or you can open a new editor end thus increase the amount of open tabs (the unobtrusive choice). if you want to ensure some tabs never get closed autmatically, you can pin them. this by clicking on the pin icon (the rightmost icon in the toolbar, with “pin editor” as tooltiptext).

  2. go to windows -> preferences -> validation and uncheck any validators you don’t want or need.

  3. go to windows -> preferences -> general -> appearance -> and uncheck any animation you don’t want or need.

  4. go to windows -> preferences -> maven and check 'do not automatically update dependencies'.


not to be underrated is having a fast machine. 16-32 gb of ram, ssd and a decent processor... and who0o0om there you go.


make an effort to configure your build path. code completion uses a lot of memory if it has to go through your whole project folder.

  • right click on your project and choose preferences.
  • choose your build path setting and remove your project folder.
  • then add only the folders where you have your source code and library code.


best practices in this thread are implemented in the free optimizer for eclipse, from zeroturnaround.

what does it help with?

  • insufficient memory allocation
  • class verification overhead
  • excessive indexes and history
  • obsolete or slow jdk
  • eclipse being out of date
  • lengthy build and redeploy times

for more details, check out this article from rebellabs.


one more trick is to disable automatic builds.


i also tuned vmargs and stuff. but what really sped up eclipse on windows is the "proper" configuration of the anti-virus software. you have to disable the on-demand scanning of packed files. jar files, and many files related to java are packed with pkzip algorithm to spare space. because eclipse uses tons of java files, an anti-virus attempts to individually unpack and scan every one of them. so for windows platform: turn off the on-demand scanning of packed files, otherwise eclipse will be unusably slow. please keep in mind, that disabling this unfortunately makes your system weaker against attacks, most of the malware use packers.


i experienced a considerable improvement in performance when limiting the number of open tabs (in the past i frequently had 30+ tabs open). you can let eclipse handle this for you automatically:

window -> preferences -> editors -> close editors automatically

8 open tabs is the amount before the >> sign appears, so i tend to leave it at 8.

when opening more tabs, the ones the least recently accessed will be closed.

->when all editors are dirty or pinned

if it has unsaved modifications you can prompt to save & reuse (tab will be closed, a new one will be opened in its place). or you can open a new editor end thus increase the amount of open tabs (the unobtrusive choice).

if you want to ensure some tabs never get closed autmatically, you can pin them. this by clicking on the pin icon (the rightmost icon in the toolbar, with "pin editor" as tooltiptext).


i implemented a plug-in to configure which features to be loaded in runtime to improve the performance and reduce the conflict among different plug-ins.

you may have installed many features into your eclipse, such as android development tools, c/c++ development tools, php, svn, git and clearcase plug-ins. hence eclipse is heavy and costs a lot of memory, and some of them are not often used.

so you could use my tool to create different runtime policies, such as one that has android, git and base eclipse, another one contains c/c++, svn and base eclipse. next time eclipse would only load the specified features if you're using the policy that only has android and git.

you are welcome to try it and give me the feedback. :)

the name of that tool is equinox advanced configurator.


along with the latest software (latest eclipse and java) and more ram, you may need to

  • remove the unwanted plugins (not all need mylyn and j2ee version of eclipse)
  • unwanted validators
  • disable spell check
  • close unused tabs in java editor (yes it helps reducing eclipse burden)
  • close unused projects
  • disable unwanted label declaration (svn/cvs)
  • disable auto building



i give it a ton of memory (add a -xmx switch to the command that starts it) and try to avoid quitting and restarting it- i find the worst delays are on startup, so giving it lots of ram lets me keep going longer before it crashes out.


there is another thing that really speeds up eclipse on both windows and especially linux - putting the jvm in ram disk.

for windows you can use the commercial ram disk driver from qsoft.

for linux use any of the methods described in numerous articles on the internet. it is important to give additional space to the ram disk that is 10% bigger than the size of the jvm.

check it out. it really makes a difference.


eclipse loads plug-ins lazily, and most common plug-ins, like subclipse, don't do anything if you don't use them. they don't slow eclipse down at all during run time, and it won't help you to disable them. in fact, mylyn was shown to reduce eclipse's memory footprint when used correctly.

i run eclipse with tons of plug-ins without any performance penalty at all.

  • try disabling compiler settings that you perhaps don't need (e.g. the sub-options under "parameter is never read).
  • which version of eclipse are you using? older versions were known to be slow if you upgraded them over and over again, because they got their plug-ins folder inflated with duplicate plug-ins (with different versions). this is not a problem in version 3.4.
  • use working-sets. they work better than closing projects, particularly if you need to switch between sets of projects all the time.

it's not only the memory that you need to increase with the -xmx switch, it's also the perm gen size. i think that problem was solved in eclipse 3.4.


disable virus scanners, or at least configure any virus scanner to not scan jar files on read access.


while not directly related to eclipse:

if you're running windows 7 (and presumably windows vista), be sure to disable the file indexing of your workspace folder if your stuff is is in the default place - your home folder. windows by default indexes everything in you home folder, and it's normally just a waste for your workspace. (right click the workspace folder in explorer , properties -> advanced.)


another performance boost can be gained by disabling label decorations (windows -> preferences; general -> appearance -> label decorations) and by disabling unused capabilities on startup (windows -> preferences; general -> startup and shutdown).

you may also get additional performance by choosing a different garbage collection strategy depending on your jvm.

if you're fed up with restart cycles you could use javarebel from zeroturnaround. that will shorten your time spent on server/client restarts.


thanks for the hints. these options (mentioned above) helped me a lot:


increasing memory & regarding to my updated java version in eclipse.ini:


additionally, since we are optimizing for speed, setting -xms to the same value as -xmx makes the jvm start with the maximum amount of memory it is allowed to use.

linux / ubuntu:


update-alternatives --config java


close any open projects which are not in current use.

try to switch off the auto publish mode during development.


make sure that you're using the sun jvm to run eclipse.

on linux, particularly ubuntu, eclipse is installed by default to use the open source gcj, which has drastically poorer performance. use update-alternatives --config java to switch to the sun jvm to greatly improve ui snappiness in eclipse.


go to windows -> preferences -> validation and uncheck any validators you don't want or need.

for eclipse 3.7, you use windows -> preferences -> general -> startup and shutdown.


add -xverify:none to your eclipse.ini file.

it will cut down your eclipse startup time considerably (50% in my case if not more). this will tell the vm not to validate all the .class files it is loading.

consider this: never disable bytecode verification in a production system (as mentioned in the comments)

Related Query

More Query from same tag