This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 58779 - Init of websvc.registry module takes ages
Summary: Init of websvc.registry module takes ages
Status: VERIFIED FIXED
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Martin Grebac
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2005-05-11 13:39 UTC by _ rkubacki
Modified: 2005-12-01 00:36 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
New version of module installer. (10.01 KB, text/plain)
2005-08-31 16:08 UTC, Martin Grebac 		Details
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 _ rkubacki 2005-05-11 13:39:50 UTC 
Trying with dev build from May 10, JDK 1.5.0_02

The IDE with three J2SE projects start in 12 seconds but startup logging shows
that 1 second is spent in module install of websvc registry. I do not know why
initializes all plugins and J2EE platforms as I did not touched any websvc
related functionality.
Comment 1 Martin Grebac 2005-08-30 13:31:36 UTC 
Radime, would it be possible to re-measure with latest build? We did some bigger
changes in the jars and the registry loading (not directly aimed to fix this
bug, this was another issue). It would help us to know if it's better or worse
now. I'd say it should not load that many jars and that many plugins now, but
who knows.
Thanks.
Comment 2 _ rkubacki 2005-08-31 15:02:59 UTC 
You can get the numbers w/ -J-Dorg.netbeans.log.startup=print flag. It is not 1
second now but still 0.24 of 14 seconds. It means we spent almost 2% of startup
here (including classpath scanning). I get these numbers whean starting IDE with
two simple J2SE projects opened.

I suggest to lower priority but still we should try to make it faster.
Comment 3 Martin Grebac 2005-08-31 16:06:19 UTC 
 I think we can fix it. I'll attach new version of ModuleInstaller which loads
jars on first request, so please confirm it fixes the perf problem (I checked
with the flag and as far as I can say it does so - load time is 1ms).
 I'd like to hear your opinion before I integrate, and would like to pass it to
QE first as well for sanity check so that I don't cause any regression.
Comment 4 Martin Grebac 2005-08-31 16:08:49 UTC 
Created attachment 24424 [details]
New version of module installer.
Comment 5 Lukas Jungmann 2005-08-31 18:00:25 UTC 
Fix seems to not cause any regression.
Comment 6 _ rkubacki 2005-09-01 08:46:52 UTC 
nice from perf. point of view. 

Also if you could avoid Empty class (s/new
Empty().getClass()/WebServiceModuleInstaller.class/) it would be even better.
Comment 7 Martin Grebac 2005-09-01 10:31:13 UTC 
Fixed in trunk:
http://websvc.netbeans.org/source/browse/websvc/registry/src/org/netbeans/modules/websvc/registry/netbeans/WebServiceModuleInstaller.java?r1=1.11&r2=1.12

The Empty class seems to be really a minor issue. I didn't (quickly ;O) ) find
an easy way of fixing it, so if you have any suggestion, you're welcome.
Comment 8 Martin Grebac 2005-09-01 12:02:52 UTC 
I've read your comment once more, so the Empty class is removed now ;O) 
http://websvc.netbeans.org/source/browse/websvc/registry/src/org/netbeans/modules/websvc/registry/netbeans/WebServiceModuleInstaller.java?r1=1.12&r2=1.13
Comment 9 Lukas Jungmann 2005-12-01 00:36:28 UTC 
v.