Community
Participate
Working Groups
Using 3.3 M7 but already exists since at least 3.2. This bug is the follow-up of bug 185452 comment 3... While searching for package declaration, lot of duplicates are reported. This is not a consequence of the fix for bug 183062, duplicate matches were already reported since at least 3.2.
Created attachment 66723 [details] Proposed patch
Here are the numbers for the testGotoPackage performance test: 3.2: 273.3ms +/- 2.6ms 3.3 M7: 483.2ms +/- 1.6ms patch: 264ms +/- 2.8ms For the testSearchPackageDeclarationsWorkspace performance test: 3.2: 614ms +/- 2.4ms 3.3 M7: 528.2ms +/- 12.5ms patch: 289ms +/- 2.5ms So, fixing this problem will obviously improve results for bug 185452...
Jerome, I'm not sure if the 2 performance tests will be really added, but I have kept them in the patch to be able to rerun them if we need to get more numbers...
I think the change that consists in using fragment.getJavaProject() is not needed. It should be using javaProject as before. Other than that the patch looks good.
Created attachment 66891 [details] New proposed patch New patch not including the unnecessary change.
Released for 3.3 RC1 in HEAD stream. Note that I have released Search perf tests changes but only one test is activated (search package declarations on a workspace scope). I've also released corresponding change in perf_32x branch.
Verified for 3.3 RC1 using build I20070515-0010.