Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 369581 - HierarchyIndexColumn class had an inefficient algorithm
Summary: HierarchyIndexColumn class had an inefficient algorithm
Status: CLOSED FIXED
Alias: None
Product: OSEE
Classification: Technology
Component: Action Tracking System (ATS) (show other bugs)
Version: 0.9.9   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 0.9.9   Edit
Assignee: S. Cook CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-24 14:37 EST by S. Cook CLA
Modified: 2012-01-24 18:34 EST (History)
1 user (show)

See Also:

Attachments
HierarchyIndexColumn class had an inefficient algorithm (4.32 KB, patch)
2012-01-24 14:40 EST, S. Cook CLA 		ryan.d.brooks: iplog+
Details | Diff
View All 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 S. Cook CLA 2012-01-24 14:37:21 EST 
HierarchyIndexColumn class had an inefficient algorithm that, when combined with a large data set (ie: 26,000+), took a very long time to run.  The computeHierarchyIndex() and getPosition() were being used over and over to determine the hierarchy index values.  We made use of a MapMaker - a map that assigns an expiration timer to each item that is added to the map - which acts as a cache and interrupts the horribly inefficient recursive calls.
Comment 1 S. Cook CLA 2012-01-24 14:40:50 EST 
Created attachment 210000 [details]
HierarchyIndexColumn class had an inefficient algorithm