Bugzilla – Full Text Bug Listing
| Summary: | Run configuration dialog takes long to open | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Wim Jongman <wim.jongman> |
| Component: | Debug | Assignee: | Platform-Debug-Inbox <platform-debug-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | curtis.windatt.public, darin.eclipse |
| Version: | 3.6 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Wim Jongman
I've never seen it take that long to open. What sort of launch configuration is selected once the dialog is opened? How many launch configurations do you have?Is moving between configrations slow? The LCD selects the last launched config when opened. I am wondering if this is a performance issue with a specific config type, or the dialog in general. (In reply to comment #1) Maybe a minutes is not true but a good 30 seconds is not uncommon. Most of the times an "eclipse launch" is opened as the first LC. Launching itself is almost instant, also if i choose the run button in a product configuration where it creates a new LC is quick enough. Are there specific reasons why it is such a slow dialog? The Eclipse launch configurations have some performance issues (a combination of loading plugin models, populating a tree with all the models and collection tracing information). However, there was some performance enhancements in 3.6 (lazy loading of the tree and tracing info). Do you have a large number of plug-ins in the workspace or target? Do you have tracing options turned on? Do you have a subset of plug-ins selected on the plug-ins tab? Hi, Opening for the first time indeed takes more than a minute (scientificly proved by counting 1-mississippi, 2-mississippi, ..). I have a dual core 3gb machine. Not the latest and the greatest but still a decent development machine with 80% of RAM occupied and a processor use of 5% at the time of opening. A heap size of 258M with 495M max. Opening the Run configs dialog for the second time takes about 6 seconds. about the time needed to switch from run config to run config. I have 63 launch configurations of which 53 are visible according to the message (although no filter has been set). I have no tracing options set and the selected run configuration does contain a subset of plugins. (In reply to comment #4) > I have 63 launch configurations of which 53 are visible according to the > message (although no filter has been set). I have no tracing options set and > the selected run configuration does contain a subset of plugins. Do you have a very large target platform? My guess is that it's the Eclipse launch config plugins tab that is causing the slowness. Though usually large delays are only seen when you have >1000 plug-ins. Bug 302503 is one thing we might do to try and improve performance. Just to confirm, please set up the following and see if performance improves: 1) Create a new Eclipse launch config 2) Ensure that the plug-ins tab is using all workspace/external plug-ins and that the tree is empty and disabled. 3) Close the launch configuration dialog 4) Open the launch configuration dialog (it should open the same config) = If performance improves, the plug-ins tab is causing your problem. Hi Curtis., Yes, I have 2900 plugins (c:\program files\IBM\SDP). Just loading the contents of the target in the preference's target dialog takes a loooong time. That could definitively cause it. (In reply to comment #6) > Hi Curtis., Yes, I have 2900 plugins (c:\program files\IBM\SDP). Just loading > the contents of the target in the preference's target dialog takes a loooong > time. That could definitively cause it. I'm going to mark this as a dupe of bug 302503 then. I'll bump up that bugs priority a bit too. There are definitely some gains to be had there, but I'm concerned that changing that tab could be a big time sink. *** This bug has been marked as a duplicate of bug 302503 *** |