StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>There are a couple of questions/answers on SO that might help you :</p> <ul> <li><a href="https://stackoverflow.com/questions/316265/tricks-to-speed-up-eclipse">Tricks to speed up Eclipse</a></li> <li><a href="https://stackoverflow.com/questions/423270/how-to-speed-up-the-eclipse-project-refresh">How to speed up the eclipse project ‘refresh’</a> ; I'm using the <a href="http://andrei.gmxhome.de/filesync/" rel="nofollow noreferrer">filesync</a> plugin suggested there every day, and it's a real pleasure : 10 seconds for an SVN update, instead of 5 to 8 minutes <em>(my files being on a network drive)</em> ; same when launching Eclipse, as it was the "project refresh" that took time, exactly like you described.</li> <li><a href="https://stackoverflow.com/questions/957488/eclipse-optimizations">Eclipse optimizations</a></li> </ul> <p>Maybe those posts will help you at least a bit :-)</p> <p>If not : can you tell us a bit more about your set up ? Which plugins are you using, how big are your projects, which OS do you use, what kind of computer (CPU, RAM, ...) do you use ...</p> <p><br> One thing that will help for sure, is getting more RAM, at least if you only have 1 GB : that's definitly not enough for Eclipse ; in my opinion, 2 GB is the minimum required, if you want to be able to run anything else (browser, mail, whatever, ...) at the same time.</p> <p>Couple of other ideas include :</p> <ul> <li>Using sun's JVM ; using the last version is probably a good idea</li> <li>Using the latest version of Eclipse, too <em>(For PHP, I've seen great things when switching from PDT 1.x to 2.x, at least)</em></li> <li><a href="https://stackoverflow.com/questions/142357/what-are-the-best-jvm-settings-for-eclipse">Configure your JVM / eclipse.ini properly</a></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload