Summary: | perf problem with external JARs | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Philipe Mulet <philippe_mulet> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P2 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0 M4 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
Philipe Mulet
2002-02-27 05:13:38 EST
We need to investigate our story here. I am suspecting that each shared JAR is opened quite a number of times (once per reference). This sounds true for both the builder and the JavaModel. In the case of the JavaModel, it might be possible to improve this given we share elements underneath. On the builder front, I don't see how we could improve this given we have no hook into the build manager, just on project build operations. Maybe we could setup a cache in the JavaModel manager and use a POST_BUILD delta notification to clear this cache ? Interesting comment in the same area (http://bugs.eclipse.org/bugs/show_bug.cgi? id=10216). Now caching the existence check result on external jars. This cache is flushed before building, so that the builder can discover that some external jars have been deleted. |