| Summary: | [performance][context] any user interaction takes minutes of CPU load for large projects if Focus is enabled in Package Explorer | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Missing name <eclipse.org> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | RESOLVED WORKSFORME | QA Contact: | Shawn Minto <shawn.minto> |
| Severity: | major | ||
| Priority: | P1 | CC: | eric-karl, jtk499, steffen.pingel |
| Version: | 3.4 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 267143 | ||
| Attachments: | |||
Created attachment 172788 [details]
CPU usage while opening a file
Looking at the provided stack trace, it seems that the automatic linking is being the problem. Without a task active, can you enable the "Link with Editor" feature in the package explorer (the toolbar button with the arrows pointing both ways) and see if you have a similar problem (especially when the Package Explorer is collapsed and you use "Open Type" or "Open Resource" to open a file). Since it seems to be frozen for a long time, do you think that you could get a few stack dumps during that time frame so we can see if this is what is causing the problem or if that just happened to be running when you took the stack dump? Also, how large are the monolithic projects so that I can try to reproduce this here? Created attachment 172917 [details]
Threaddump while activating a task (1/5)
Created attachment 172918 [details]
Threaddump while activating a task (2/5)
Created attachment 172919 [details]
Threaddump while activating a task (3/5)
Created attachment 172920 [details]
Threaddump while activating a task (4/5)
Created attachment 172921 [details]
Threaddump while activating a task (5/5)
(In reply to comment #2) Thanks for your quick reply! I have taken a series of threaddumps with one large project open. It was the first time of opening the Task List and activating one local task. They are each about 1 minute apart. If "Link with Editor" is enabled and Mylyn disabled (by closing the Task List), files are opened quickly in about 2 seconds. One of the large projects has 22000 Java-Files in about 7300 directories (didn't count the packages exactly). Thanks for all of the additional stacks and the testing! After looking at this more, it seems that the problem is due to the focusing trying to load the Java model for these large projects which can take a lot of time. I will have to look into this to see if there is anything that we can do to improve the performance for projects this large. An upgrade to Eclipse 3.6 with Mylyn 3.4 did not make a difference. Steffen: Could you summarize how bad or common this problem is? Wondering if we need to schedule it for 3.6. I have upgraded to 3.4.3 and this problem is totally gone. Everything is superfast as it should be. I'm happy! I close the issue as fixed, because noone else reported it. |
Created attachment 172787 [details] Threaddump while waiting for a file to be opened Any user interaction if Mylyn is enabled such as - activating a task - opening a file - expanding a tree node in the Package Explorer takes literally minutes (1–3 minutes depending on the interaction) where the UI is frozen and Eclipse is using up one CPU core completely. As a workaround one can disable Focusing in the Package Explorer, but of course one loses one of the more important features of Mylyn by this. I had 2 small projects and 2 large, monolithic projects open. Project size seems to matter, because I don't see the issue with only small projects open. Eclipse version: 3.5.2