Community
Participate
Working Groups
The computation of the adornment flags for the PackagesView can take as long as 1300 ms if you create a workbench with all of Eclipse loaded with source and then switch to the Java Perspective. The method ErrorTickAdornementProvider.computeAdornmentFlags is the one this timing was taken for with OptimizeIt.
How many errors did the workspace have? Could please attache the optimize it trace. It is easy to export a trace as html. Seeing the number 1300ms is not very helpfull.
There were approximately 11,000 errors in this case. I will run it again and get a stack trace.
Todd, do you think it is still a problem or can we close this one?
sorry for misspelling your name, Tod
I will need to bench again to be sure. And no problem about mispelling the name - it is a wierd one if you live in a German speakingcountry anyways <grin>...
Created attachment 2615 [details] computeAdornmentFlags
computeAdornmentFlags takes 1% of startup time (52 error-markers in workspace)
Created attachment 2616 [details] computeAdornmentFlags2 nope, it's more because it's called via multiple paths - find 'computeAdornmentFlags' in the trace attached
it's slow because collecting markers is slow. see bug 11164
on a big workpace (820 markers) computeAdornmentFlags takes 13-14 % all of which is spent in collecting markers. considering making this bug depend on bug 11164.
this is a dup of bug bug 11164 really *** This bug has been marked as a duplicate of 11164 ***