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

Eclipse会延迟加载插件，大多数常见的插件， 比如Subclipse，如果你不使用它们，就不要做任何事情。 它们在运行时完全不会降低Eclipse的速度，而且它 不能帮你让他们失效。事实上，Mylyn被展示过 在正确使用Eclipse时减少内存占用。

我运行Eclipse时使用了大量的插件，但没有任何性能 罚点球。

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.

使用-Xmx不仅需要增加内存 开关，这也是烫发的大小。我认为 在Eclipse 3.4中解决了这个问题。

增加你的内存到8 GB以上，并禁用自动构建项目。这对我很管用。

也试试这个，它会提高性能:

清理索引-{工作区 路径}.metadata.plugins \ org.eclipse.jdt。核心清理历史—— {工作区 路径}.metadata.plugins \ org.eclipse.core.resources.history

清理上述文件夹不会影响项目文件。

试试这些。有两种方法。

第一个过程

参考这篇文章。

http://www.javacodegeeks.com/2014/06/the-real-way-to-make-eclipse-run-faster-on-ubuntu.html

第二个过程。

在终端执行命令。

ramdisk

为Ubuntu获得更好的性能和更快的响应。

Ramdisk是系统内存的一部分。Ubuntu默认使用物理内存(RAM)的一半作为ramdisk，并将其挂载到RAM上

/dev/shm

，它可以像普通磁盘空间一样使用(创建文件和文件夹，并以更好的性能操作它们，而不是将它们存储在硬盘上)。如果ramdisk使用了超过一半的RAM，则数据将被转移到交换空间。如果ramdisk使用更少的内存，剩余的内存仍然可以做RAM正在做的事情。

设置ramdisk上限

如上所述，默认情况下，ramdisk可以使用一半的RAM。如果您想更改上限，请执行以下步骤:

使用您最喜欢的编辑器编辑/etc/fstab: Gksudo gedit /etc/fstab .使用实例 找到这一行并更改它使其看起来像这样(如果不存在则添加这一行，并将512M更改为您喜欢的内容): tmpfs /dev/shm tmpfs默认值，size=512M 0 0 重启或重新挂载 /dev/shm

将/tmp挂载到ramdisk上

为了便于使用，可以将目录挂载到

/dev/shm

通过以下命令:

mkdir /dev/shm/tmp

chmod 1777 /dev/shm/tmp

绑定/dev/shm/tmp /tmp

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

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

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