Summary: | Openable.hasChildren is slow | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Adam Kiezun <akiezun> | ||||
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> | ||||
Status: | RESOLVED WORKSFORME | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | Keywords: | performance | ||||
Version: | 2.1 | ||||||
Target Milestone: | 2.1 M4 | ||||||
Hardware: | PC | ||||||
OS: | Windows 2000 | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Adam Kiezun
2002-12-09 05:28:31 EST
Created attachment 2721 [details]
expanding/collapsing nodes in packeage explorer 2
like expanding/collapsing nodes in the package explorer
where it consumes almost 67%
It has to do some work: i.e. open the corrresponding resource and expand it to find out that it has some children. Maybe we could always answer true on some kinds of resources (like JARs)... Do you have particular scenarii where it specially takes some time ? the scenario is expanding a node in the package expolorer (project or source folder) *** Bug 27924 has been marked as a duplicate of this bug. *** Adam, how do you take the measure? When I expand a node, I don't have time to start and stop the CPU profiler. Do you have a test case where expanding a node takes more than half a second? try Jeff's bigworkspace start profiling before expanding stop after expanding When doing so, I see it takes 165ms in AbstractTreeViewer.handleTreeExpand() to expand the tree on the 'org.eclipse.core.tests.resources' node. Which node did you chose to get 1003ms in AbstractTreeViewer.handleTreeExpand()? try expanding org.eclipse.swt I now see 187ms spent in hasChildren when expanding org.eclipse.swt. Closing. |