Community
Participate
Working Groups
While investigating bug 95328 (Run on Server wizard slow the first time), I traced WTP plugin startup times and found that almost a second and a half of time is spent just activating plugins, before any API is even called. Most plugins started in well under 20ms, but several were very slow. The third worst offender is the wsdl plugin: org.eclipse.wst.wsdl.validation - 141ms Eclipse guidelines say that plugins should not do any large calculations or initialization in their startup() methods - these should be deferred to when they are required by API calls. This slow startup is even affecting plugins like server tools due to indirect dependencies through other parts of WTP. You can trace this using the debug/bundleTime flag in org.eclipse.osgi.
I'll try profiling to see what's going on.
Amy, please add this to your list of things to profile.