Community
Participate
Working Groups
Created attachment 132815 [details] trace I20090421-0930, I guess this is a consequence of the fix for bug 271102 With this build, normal Save actions in a Java Editor often take a long time. I took a trace (sampling) and saw that most of the 4 seconds were spent in DeltaProcessor#resourceChanged(IResourceChangeEvent), split up in two invocations, one from the CleanUp (Save Action), and the other from the actual save operation.
This regression is also seen in our JDT/Core model performance test: testCloseProject() (see bug 270784).
Created attachment 132915 [details] Proposed fix
(In reply to comment #2) > Created an attachment (id=132915) [details] > Proposed fix > Here are the numbers I get for the Elapsed Process: v_949 + bug 270784 fix: 1.08s (95% in [997ms, 1.16s]) v_950: 7.14s (95% in [6.69s, 7.59s]) v_950 + proposed fix: 0.992s (95% in [885ms, 1.1s])
(In reply to comment #3) > (In reply to comment #2) > > Created an attachment (id=132915) [details] [details] > > Proposed fix > > > Here are the numbers I get for the Elapsed Process: > v_949 + bug 270784 fix: 1.08s (95% in [997ms, 1.16s]) > v_950: 7.14s (95% in [6.69s, 7.59s]) > v_950 + proposed fix: 0.992s (95% in [885ms, 1.1s]) > As per Jerome's remark, I forgot to say that these numbers are times for the JDT/Core perf test testCloseProjects()...
Fix released for 3.5M7
Verified for 3.5M7 using Frederic's performance numbers
*** Bug 274232 has been marked as a duplicate of this bug. ***