Why Eclipse’s “Check for Updates” is horribly slow (and how to fix it)
I recently installed Eclipse Indigo. I wanted to add a few plugins to it, so I tried to use the UI to check for new updates and install some new packages. I let it run for a while, and after about 45 minutes, it looked to be about 20% done. Eventually, it displayed a few errors about timing out.
The issue is that Eclipse appears to be trying to contact mirrors that don’t have a proper copy of all the files it’s expecting. My solution was to invoke eclipse with the following flag. Add it after “eclipse”, or in eclipse.ini
-Declipse.p2.mirrors=false
7 Comments
Brad
Monday, 31 October 2011For the love of all that is holy, THANK YOU!
Dan Green
Wednesday, 30 May 2012Words cannot describe how awesome you are…
Sergey
Thursday, 7 June 2012Unbelievable! Eclipse has been upgrading for 10 hours. But when I added this option It had completed in ten minutes.
Thank you very much.
Guillaume
Monday, 11 June 2012Thanks for the tip ! It was so slow before, I was wondering why causes it.
Why Eclipse's “Check for Updates” is horribly slow (and how to fix it … | Laughing
Wednesday, 20 June 2012[…] Visit link: Why Eclipse's “Check for Updates” is horribly slow (and how to fix it … […]
Fiona Coulter
Friday, 10 May 2013Thanks. I was trying to update eclipse, it kept getting stuck trying to download one particular file. Very frustrating! This solved the problem
Rein
Monday, 19 August 2013Unbelievable indeed: instead of days of upgrading/downloading additional plugins, it now takes only a couple of minutes (for my helios version of eclipse).
Thanks, thanks, thanks….