Bug 12605 - JavaIndexing time consuming on import
Summary: JavaIndexing time consuming on import
Status: RESOLVED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Dejan Glozic CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2002-04-02 09:08 EST by Tod Creasey CLA
Modified: 2002-04-16 15: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 Tod Creasey CLA 2002-04-02 09:08:19 EST 
When you choose to import all of Eclipse with source the JavaIndexing thread 
will take 204,248 ms (about 3 1/2 minutes) with auto build off. 

With auto build on it takes 511,958 ms (about 8 1/2 minutes) - perhaps turning 
it off for the duration of the import and then doing a bebuild all afterwards 
might help.
Comment 1 Tod Creasey CLA 2002-04-02 09:13:25 EST 
WorkspaceModelManager spends 6990 ms processing resource changes regardless 
most of that is in createWortkspacePluginModel (4786 ms).
Comment 2 DJ Houghton CLA 2002-04-02 09:41:53 EST 
Moving to PDE/UI for comment.
Comment 3 Dejan Glozic CLA 2002-04-16 15:56:56 EDT 
PDE needs some time to digest all the plug-ins (parsing the manifests and 
building the models). This time has been significantly reduced in the default 
case because the models are loaded directly from the live registry (no parsing 
is involved). This covers majority of the cases. The rest (targeting another 
Eclipse application) will still have a parsing hit but due to a less frequent 
usage is not considered critical.