Bug 94436 - Investigate performance of project close
Summary: Investigate performance of project close
Status: RESOLVED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-10 13:32 EDT by John Arthorne CLA
Modified: 2005-05-16 17:28 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 John Arthorne CLA 2005-05-10 13:32:17 EDT 
Build: I20050509-2010

Closing a large number of projects is slow.  Investigate where the time is going.
Comment 1 John Arthorne CLA 2005-05-10 13:51:00 EDT 
I created a workspace containing platform-core and platform-ui modules. This
contains 18 projects.  I closed and reopened all projects once before starting
to measure, to make sure everything was warmed up.  On the second run of closing
all projects:

Total time: 9.75 seconds
3.5 seconds in pde.internal.core.WorkspaceModelManager
1.9 seconds in jdt.internal.core.DeltaProcessingState
0.2 seconds in other miscellaneous listeners.

This leaves about 4 seconds for writing all the project tree state to disk.
Comment 2 John Arthorne CLA 2005-05-10 13:55:08 EDT 
Same test case right after startup in Java perspective:

Total time: 10.8 seconds
PDE listener: 5.4 seconds
JDT listener: 1.5 seconds
Other: 0.2 seconds
Core resources: 3.7 seconds
Comment 3 John Arthorne CLA 2005-05-16 17:28:17 EDT 
Closing.  Profiling showed nothing exceptional.  Closing projects is I/O
intensive since it is writing all tree and model states to disk.