Bug 51244 - [Decorators] DecorationScheduler performance
Summary: [Decorators] DecorationScheduler performance
Status: CLOSED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Tod Creasey CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-05 11:57 EST by Dani Megert CLA
Modified: 2005-05-10 14:56 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2004-02-05 11:57:43 EST 
I20040204

I was tracing performance when opening an editor and found that > 7% is spent
when the decoration scheduler calls toString() on the elements for the subTask
label.

This can be expensive: in my scenario it was calling this *lots* of times upon
JavaElement which at the end spends time in String.substring (I filed separate
bugs against JDT Core and Platform Core).

I doubt you can do much except updating the subtask label less frequently.
Comment 1 Dani Megert CLA 2004-02-06 08:39:05 EST 
Please note that when using builds > 20040206 you might not see this because J
Core already improved the code (see bug 51249).
Comment 2 John Arthorne CLA 2004-02-09 16:12:20 EST 
This seems like an excessive level of detail in the progress feedback 
for decoration job... I would be inclined to make the decoration job into a 
system job and not display any progress at all.
Comment 3 Tod Creasey CLA 2004-03-18 09:25:50 EST 
Decoration is now a system job.
Comment 4 Tod Creasey CLA 2005-05-10 14:56:33 EDT 
Marking closed