这个线程中的最佳实践是在ZeroTurnaround的免费Optimizer For Eclipse中实现的。

它有什么帮助?

内存分配不足 类验证开销 过多的索引和历史记录 过时或缓慢的JDK Eclipse已经过时 漫长的构建和重新部署时间

要了解更多细节，请查看RebelLabs的这篇文章。

如果Eclipse运行缓慢，我遵循以下几个步骤:

Any unused plugins installed in Eclipse, should uninstall them. -- Few plugins makes a lot much weight to Eclipse. 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. Change the type filters. It facilitates to specify particular packages to refer always. 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. Un-check auto build always. Particulary, Maven project's auto build is useless. Close all the files opened, just open current working files. Use Go Into Work sets. Instead of complete workbench. 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.

我已经禁用了Windows > Preferences > General中所有未使用的选项，它对性能有巨大的积极影响，eclipse在切换选项卡时仍然很慢，我不想增加内存，但在滚动时要快得多。谢谢你的提示。

另一个技巧是禁用自动构建。

在eclipse.ini文件中添加-Xverify:none。

它将大大缩短Eclipse启动时间(对我来说是50%，如果不是更多的话)。这将告诉VM不要验证它正在加载的所有.class文件。

考虑一下:永远不要在生产系统中禁用字节码验证 (如评论所述)

你有大的公羊吗?创建一个ramdisk，并把你的

JDK JVM Eclipse 工作空间

确保将更改保存回HDD或提交给VCS，以避免断电时数据丢失。