Bug 180498 - [search] "Search constructor occurrences" perf test is getting slower
Summary: [search] "Search constructor occurrences" perf test is getting slower
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2007-04-02 11:18 EDT by Frederic Fusier CLA
Modified: 2007-05-02 07:17 EDT (History)
0 users

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 Frederic Fusier CLA 2007-04-02 11:18:11 EDT 
Since build I20070110-1600 "Search constructor occurrences" test (ie. FullSourceWorkspaceSearchTests#testSearchConstructor) has following numbers on releng performance tests results DB:
 - lnx1_R3.3: -2.71% < time < -0.48%
 - lnx2_R3.3: -0.77% < time < 1.15%
 - lnx3_R3.3: -0.44% < time < 1.21%
 - win1_R3.3: -1.07% < time < 1.21%
 - win2_R3.3: -1.09% < time < 1.28%

So, we need to improve this kind of search to have no negative results (especially on lnx1_R3.3 test box)...
Comment 1 Frederic Fusier CLA 2007-05-02 07:17:09 EDT 
After JDT/Core performance tests were improved (see bug 178499) , here are the new numbers since I20070424-0930 build results:
Search constructor occurences
 - lnx3_R3.3: -0.7% < time < +0.4%
 - win2_R3.3: -0.6% < time < +0.1%
 - lnx2_R3.3: -0.2% < time < +0.8%
 - win1_R3.3: -0.6% < time < -0.1%
 - lnx1_R3.3: -0.1% < time < +0.2%

Close as INVALID as these numbers show that we're almost flat vs. 32...