Bug 131754 - [DnD] performance regression in ToolBarManager::update and DragUtil::getDisplayBounds?
Summary: [DnD] performance regression in ToolBarManager::update and DragUtil::getDispl...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC Linux-GTK
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2006-03-14 12:52 EST by Tom Hofmann CLA
Modified: 2019-09-06 15:30 EDT (History)
1 user (show)

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 Tom Hofmann CLA 2006-03-14 12:52:29 EST 
I20060301

While trying to find out the reason for the performance regression in the "Activate30JavaEditors" performance tests, the following methods stick out as taking constantly more time in I20060301 than in 3.1:

- ToolBarManager::update 
- DragUtil::getDisplayBounds
- SubActionBars::setGlobalActionHandler

The last one is probably covered by bug 126901.

The measurements indicate that the first two do not use more time themselves, but that some SWT calls take longer. I filed bug 131107 to investigate this. 

Can you think of any reason why these methods should show a performance regression? Do you have any measurements for these methods? Thanks for any advice.
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:30:18 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.