Summary: | org.eclipse.jdt.internal.core.search.indexing.AddJarFileToIndex.execute(IProgressMonitor) causes performance degradation | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Kenneth Cheung <kennethc> | ||||
Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> | ||||
Status: | VERIFIED INVALID | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | CC: | frederic_fusier, Olivier_Thomann, satyam.kandula, srikanth_sankaran | ||||
Version: | 3.4.2 | Keywords: | needinfo | ||||
Target Milestone: | 3.6 M5 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Kenneth Cheung
2010-01-06 14:21:32 EST
Created attachment 155442 [details]
The jar file triggering the call of the method
That code has not changed since the 3.4 release. So I don't see how it could be suddenly much slower. Could you please describe how you got the numbers? Please confirm that the same jar file is indexed on both cases. Right now nothing can be done on our side as that code has not changed in the two versions mentionned in comment 0. I got a setup on a remote machine and it appears that the added jar file only contains source files. I have observed that the AddJarFileToIndex.execute method is never called during the test! Hence, close this bug as invalid... Verified for 3.6M5 using Build id: I20100122-0800 Verified. |