Summary: | changing classpath causes significant recompilation | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | John Wiegand <John_Wiegand> |
Component: | Core | Assignee: | David Audel <david_audel> |
Status: | VERIFIED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0 F2 | ||
Hardware: | PC | ||
OS: | Windows 2000 | ||
Whiteboard: |
Description
John Wiegand
2002-05-29 20:14:50 EDT
With org.eclipse.compare it took 8 seconds to rebuild the project (because of the classpath change) and 6 seconds to propagate all the 'new' class files to its dependent projects. I don't see how dependent projects can know the 'new' class files from the full build were the same... JW: Did it take considerably longer for you? I should have flagged the time. I have rerun the test. My time (from the time I remove boot from compare's build path until the dialog disappears) is 30 seconds to compile compare + 30 seconds for the dependents - a 1 minute operation By upping my memory from the default to 256M, the time became 15 seconds! I was at the threshold and must have been getting many GCs. Sorry for the red herring. Closed. Verified. |