Summary: | [model] closing a single project causes all variables and containers to be saved | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Eric Jodet <eric_jodet> | ||||||||||
Component: | Core | Assignee: | Eric Jodet <eric_jodet> | ||||||||||
Status: | VERIFIED FIXED | QA Contact: | |||||||||||
Severity: | enhancement | ||||||||||||
Priority: | P3 | CC: | frederic_fusier, jerome_lanneluc, philippe_mulet | ||||||||||
Version: | 3.3 | Keywords: | contributed, performance | ||||||||||
Target Milestone: | 3.3 M7 | ||||||||||||
Hardware: | PC | ||||||||||||
OS: | Windows XP | ||||||||||||
Whiteboard: | |||||||||||||
Attachments: |
|
Description
Eric Jodet
2007-02-21 02:09:34 EST
Created attachment 59455 [details]
Proposed fix
The saving method of the JavaModelManager was modified to use the information available in the ISaveContext param.
This to narrow the saving of containers only to closed projects.
With this fix, I observed an average gain of 30 % on the time necessary to close the 120 projects in my test workspace.
Created attachment 59569 [details]
Proposed fix
Frédéric: as discussed, new patch with the TODO
Created attachment 61053 [details]
Performance test case
Contains the FullSourceWorkspaceModelTests::testCloseProjects test case
Patch looks good. Please release during M7. Patch released for 3.3 M7 on HEAD after resynchronization on top of v_745... Is it OK to backport this fix on R3_2_maintenance stream? For now, please just prepare the patch against R3_2_maintenance. We will decide later if this needs to be released to R3_2_maintenance Created attachment 62232 [details]
Corresponding patch for R3_2_maintenance branch
Note that this patch has been done on top of R3_2_maintenance branch which as
this time, and for the concerned modified classes, should be equivalent to
version v_686_R32x...
Verified for 3.3M7 with I20070427-0010 |