Bug 24308

Summary: Performance - Optimization of search in hierarchy
Product: [Eclipse Project] JDT Reporter: Jerome Lanneluc <jerome_lanneluc>
Component: CoreAssignee: Jerome Lanneluc <jerome_lanneluc>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: P3 Keywords: performance
Version: 2.0   
Target Milestone: 2.1 M4   
Hardware: PC   
OS: Windows 2000   
Whiteboard:

Description Jerome Lanneluc CLA 2002-10-02 07:12:40 EDT 
Build 20021001

The search using hierarchy scopes could be optimized if the match locator new 
about this special scope. The hierarchy in the scope would never need to be 
computed. Instead the match locator would relsove all potential matches and 
exclude the one that are not a super or a sub type of of the focus type.
Comment 1 Philipe Mulet CLA 2002-10-02 09:58:41 EDT 
Time permitting for 2.1, if we see performance issues with hierarchies.
Comment 2 Jerome Lanneluc CLA 2002-11-25 10:16:05 EST 
Changed SearchEngine and MatchLocator to know about HierarchyScope. When a 
Hierarchyscope is detected, its 'needsRefresh' flag is set to false, and 
MatchLocator forces a type resolve. It then excludes the matches not in the 
scope.
Comment 3 Jerome Lanneluc CLA 2002-11-26 07:43:48 EST 
Does not work for binary types. Reopening.
Comment 4 Jerome Lanneluc CLA 2002-11-26 11:43:49 EST 
Problem was that the binary type binding was cached even though there was a 
potential match in the attached source.
Now get the binding after the resolution of all potential matches.
Comment 5 David Audel CLA 2002-12-18 10:35:18 EST 
Verified.