Bug 81118 - [nls tooling][implementation Performance of property key search
Summary: [nls tooling][implementation Performance of property key search
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.1   Edit
Hardware: PC All
: P2 normal (vote)
Target Milestone: 3.1 M5   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2004-12-15 07:27 EST by Tobias Widmer CLA
Modified: 2004-12-16 03:20 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Widmer CLA 2004-12-15 07:27:43 EST 
200412142000:

Currently, performance of property key reference search degrades linear wrt 
the number of java files in the workspace. In order to improve this, the set 
of java files to be scanned could be determined by a java search for 
references to the corresponding accessor class.
Comment 1 Dani Megert CLA 2004-12-15 10:54:29 EST 
It's not only a performance benefit but also reduced the number of false positives.
Comment 2 Dani Megert CLA 2004-12-15 10:54:41 EST 
*** Bug 81140 has been marked as a duplicate of this bug. ***
Comment 3 Dani Megert CLA 2004-12-16 03:20:51 EST 
Think of this again it would be a performance loss not a gain: we have no clue
what the corresponding accessor class is. We'd have to iterate over all classes
and test whether it's an accessor and if so whether it's using that properties
files. Also note that there are neither fixed naming schemes nor location
constraints i.e. the accessor can even be anywhere in the project or even in
another one.