Eclipse easy to get stuck or a slower solution

Http://blog.sina.com.cn/s/blog_5c6c4dc90100lg8n.html
Problem:
Eclipse often stuck or building workspace wait, feel very uncomfortable, many friends may encounter such a problem, in the Internet search a solution, testing can solve the problem, the following gives a few solutions.

Solve:
1. Cancel the "project--buiild automatically" option;
2. Enter Windows->preferences->java->editor->hovers, then turn off the eclipse-related hover option;
3. Increase the maximum amount of memory used in the Eclipse.ini file-vmargs-xms40m-xmx512m;
(Eclipse.ini file parameter description can refer to http://flysheet.javaeye.com/blog/437071)
4. Unenable off the Subclipse plugin in Help->software updates->manage configration;

5. Cancellation of validation of various documents;

Eclipse 3.6 Slow Card root cause, finally found! New under the eclipse3.6, very happy, a number of new features. Not long, not much time card up, and under the most thin version of the card, looked for a long time, closed a lot of things are no use, and finally found that the original is "Usage Data Collector" This sad plugin, it will collect some user's operation information and then sent to the Eclipse Foundation, Operation More, will occupy a lot of memory, almost like a virus, to preference can see "Usage Data Collector" This option, disable off, done!resolve Eclipse Card Dead method "Turn", adjust Eclispe use memoryReduce plug-ins that start automatically after Eclipse starts
Specific operation: in Preferences, general, startup and Shutdown: Remove the items except the Plug-ins activated on startup (such as Mylyn, etc.) and remove them.
Effect: After you start eclipse, there will be a initialing Java tools scroll bar that will find a lot faster.

Reduce the need to validate the compilation of projects, increase the speed of compilation
Specific operation: In Preferences, validataion will be irrelevant validator removed, such as: I will not have nothing to do with me JPA, JSP, WS are removed.
Effect: When compiling a project, Eclipse runs a few validator projects, and it's really fast. Eclipse has been building workspace ... The problem

Version number: Eclipse SDK version:3.2.0
Phenomenon: When you start or import new project, Eclipse automatically building workspace ... This operation then continues this state no longer responds to other event actions. This is sometimes done in 10 minutes, but it is time-consuming and serious.
Solution: Check a lot of information, and finally on a BBS to find that may be the startup parameter setting problem
(http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-8253.html)
Workaround:
Method 1: Add the start parameter parameter as a post (the effect is not obvious)-vmargs-xmx256m
Method 2. Turn off the auto-build workspace: Project--Build auto .... (The effect is not obvious)

To add parameters when Eclipse starts:
-vmargs-xmx512m (Obvious effect)
Restart, building workspace ... In a short period of time to end, all normal, specific reasons can refer to the above URL in the answer, can give a lot of tips, hehe, it seems to be more information to check the benefits. Write to hope to have the same phenomenon of colleagues can refer to the solution.
See for reasons: http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-8253.html

Turn off its auto build, then increase your memory to more than 512M, Eclipse start memory loss is smaller than JBuilder, later equally fierce, notice open large eclipse memory, here is a way to prevent outofmemeory:
Http://forum.java.sun.com/thread.jspa?threadID=587273&tstart=0

Eclipse Card Death Reason

has been read 424 times 2012-4-20 23:55 | Reason, card

The night has been stuck card, die, die. WORKAROUND: 1. Remove the tick of build aotomatically under project.  2. Kill the usage Data Collector under preferences. One of the solutions to Eclipse's death ECLIPSEJVM

Updated the eclipse version in recent times, updating 3.5 and then updating to 3.6. It is easy to get stuck when editing code, especially if you want to select a block of code to copy. Originally thought to be 3.6 of the problem, back to 3.5 problems remain. Also suspected that the JVM parameter settings are too small, resulting in GC, check, my Eclipse.ini parameter is set to-xms256m-xmx1024m, is not small. Switch to the taskbar, check CPU and memory occupancy, my machine physical memory is 2G, but occupy the display is only 1.2g,cpu occupancy rate of 80%, once the card, the CPU dropped immediately, but the memory does not change anything. Should not be a GC-led issue. It must be the wrong parameter set. Think about it, why is it easy to get a card when the mouse keeps shaking on the editor? Finally thought might be with the mouse hover event to execute too often, and this event processing may be a bit of resources. OK, turn off eclipse about the hover item. See:

The hover tip is gone, but the machine is no longer stuck.

Eclipse is easy to get stuck or a slower solution