如果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.

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.

我们使用GIT作为CVS, gradle作为构建工具。

症状

在我的案例中，一个具有> 20 000个文件的特定项目在导航具有大量文件的目录时使用分层视图冻结。

Fix

创建新的Eclipse工作区 将项目重新克隆到Eclipse工作区中 将项目导入Eclipse(在本例中使用Gradle导入)

如果您因为工作等原因没有绑定到Eclipse，您需要的某些插件功能只能通过Eclipse使用等等;那么一个可能的策略就是完全摆脱Eclipse。这将极大地加快速度。

您可以切换到任何其他IDE或开发环境，以满足您的需要。NetBeans就是一个例子。一些提议的加速也适用于NetBeans，或任何其他IDE。

一个直接应用于Linux的例子是尽可能多地移动到tmpfs挂载。在NetBeans中进行Java开发时，我将Java文档和源代码移到了tmpfs挂载中，这极大地提高了性能。

同样，在c++开发过程中，如果可能的话，我将确保整个源代码树都在我的tmpfs挂载中。虽然我还没有对构建性能进行广泛的基准测试，但在合理大小的代码库(几百个源文件+头文件)上进行了一些测试，结果导致编译时间减少了50%。

请记住，使用此方法时，您的数据在断电期间不会持久。为了解决这个问题，可以创建一个脚本，将tmpfs挂载到某个备份目录，并将该脚本添加为每分钟运行一次的cronjob。

又有一个解决方案 删除这两个文件夹中的所有文件

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

这是第一次帮助。但它仍然保持缓慢

如果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.