Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 65924

Summary: Performance of plugin.xml builder is slow
Product: [Eclipse Project] PDE Reporter: Gunnar Wagenknecht <gunnar>
Component: UIAssignee: PDE-UI-Inbox <pde-ui-inbox>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: eclipse
Version: 3.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
Screenshot of progress view none

Description Gunnar Wagenknecht CLA 2004-06-07 02:20:34 EDT 
Recently we started migration of our plugins to Eclipse 3.0. We noticed that 
the performance is comparable slower when using 3.0 plugins than it is with 
the 2.1 plugins.

The plugin.xml of our main plugin id around 75k size and it needs around 20 
seconds to compile. The build progress shows "Verifying .../plugin.xml". It's 
interesting that this was noticable faster when developing against 2.1 plugins 
(imported as binary projects) using 3.0 RC1.
Comment 1 Wassim Melhem CLA 2004-06-07 10:57:26 EDT 
Note thatt binary plug-ins do/should not get validated at all by the PDE 
builder.  That is why you saw a big difference between binary and non-binary 
projects.

That 20 seconds was taken up to validate how many plugin.xml files?  what 
sizes?
We do validate every attributes and we do call the Java model to verify that 
every class you list exists, etc.  So if we are dealing with large plugin.xml 
files, then it might just be that it is a fact of life that it will 20 seconds.
Comment 2 Gunnar Wagenknecht CLA 2004-06-07 11:18:12 EDT 
20 seconds just for the one (75k) file. Not to mention the others that it 
validates.
Comment 3 Gunnar Wagenknecht CLA 2004-06-08 01:02:16 EDT 
Created attachment 11694 [details]
Screenshot of progress view

This screenshot show the build is verifying plugin.xml of jdt.ui plug-in.
According to you comment, this should not happen because jdt.ui is imported as
binary project (with real content, not with linked content).

However, verifying of jdt.ui plugin.xml (binary project) took 34 seconds which
is a lot more time that the Java build needs for a project of comparable size.

It's also noticable that the progress indicator also stays the same amount of
time at a fixed possition which leads me to say it cann't be just a forgotten
progress monitor update. Don't know.

P4 2.8 Ghz hHyperthreading CPU. The PC is usually fast (example: it only takes
14 second to build a full feature zip with all 3 plugins (around 100 classes)
using the generated build files and ANT (from within Eclipse).
Comment 4 Wassim Melhem CLA 2004-06-08 01:13:48 EDT 
The fact that a binary project was being validated is a bug that was addressed 
today (bug 65578).

I never claimed that the builder's performance is optimal.  I was just 
enquiring how slow it is for you.
Comment 5 Wassim Melhem CLA 2004-06-08 14:42:31 EDT 
*** Bug 66198 has been marked as a duplicate of this bug. ***
Comment 6 Wassim Melhem CLA 2004-06-08 18:42:57 EDT 

*** This bug has been marked as a duplicate of 66228 ***