Bug 93547 - [Presentations] WorkbenchPage#setActivePart takes 17% of the time to open editors
Summary: [Presentations] WorkbenchPage#setActivePart takes 17% of the time to open edi...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0.2   Edit
Hardware: PC Windows XP
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks: 89406
  Show dependency tree
 
Reported: 2005-05-03 11:34 EDT by Tod Creasey CLA
Modified: 2019-09-06 15:35 EDT (History)
0 users

See Also:

Attachments
OptimizeIt trace (62.80 KB, text/html)
2005-05-03 11:35 EDT, Tod Creasey CLA 		no flags Details
View All 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 Tod Creasey CLA 2005-05-03 11:34:47 EDT 
20050426 with UI loaded from HEAD

When I open the entire contents of /org.eclipse.swt/Eclipse SWT
PI/win32/org/eclipse/swt/internal/win32 using an editor with no contents the
method WorkbenchPage#setActivePart  takes 22% of the time to open.

STEPS
1) Map the java files to the performance test editor (this is just an empty label)
2) Select all of the files in /org.eclipse.swt/Eclipse SWT
PI/win32/org/eclipse/swt/internal/win32
3) Open them

Trace to follow
Comment 1 Tod Creasey CLA 2005-05-03 11:35:38 EDT 
Created attachment 20643 [details]
OptimizeIt trace
Comment 2 Paul Webster CLA 2006-09-28 14:07:30 EDT 
Is this still a problem in 3.3?

PW
Comment 3 Denis Roy CLA 2007-06-22 09:32:54 EDT 
Changes requested on bug 193523
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:35:09 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.