Bug 12606 - Workspace.endOperation can be very consuming for large operations
Summary: Workspace.endOperation can be very consuming for large operations
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: DJ Houghton CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2002-04-02 09:16 EST by Tod Creasey CLA
Modified: 2002-06-07 10:20 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 Tod Creasey CLA 2002-04-02 09:16:31 EST 
When you import the entire workbench with source using the PDE the 
Workbench.endOperation method takes 27 168 ms to run. The most time consuming 
portions are 

Workbench.broadcastChanges (21 478 ms)
  NotificationManager.notify(14 992 ms)
Workbench.snapshotIfNeeded (5 690 ms)
Comment 1 DJ Houghton CLA 2002-04-02 09:43:51 EST 
As a note, the numbers also include the time that all registered 
IResourceChangeListeners (e.g. Navigator and Task views, etc) take to process 
the deltas.
Comment 2 John Arthorne CLA 2002-04-02 12:07:56 EST 
I sent Tod a copy of our spy plugin, so that he can see how much time is taken 
by the listeners.  I don't think the snapshot time can be improved much, when 
you think about the magnitude of the change that occurred (presumably many 
thousands of resources were created).
Comment 3 John Arthorne CLA 2002-06-07 10:20:38 EDT 
.