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.
uml.project's ModuleInstall eagerly initializes nontrivial part of the uml module (hundreds of classes), which slows down the startup by >600ms (P-M@1733MHz).
changed to p3 to adhere to Netbeans priority guidelines.
krichard, I think more appropriate in this place is P2. 600ms is a huge amount of time on startup time (if you take into account the whole startup time takes around 12s on the same machine)
This issue was reported by our performance team, not by a user.
Since UML is no longer installed via an installer, I do not think that this is a valid issue any longer. We do not slow down the start up of the IDE, since the IDE is started when the user uses the update center.
low use case not currently impacting our installed user base.
fixed, on my machine it became 100ms from 400ms.
Thanks, I have measured <100ms as well (not that it can't be better, but this is certainly a big improvement). Note, that it is customary to list modified files in a closing comment to simplify verification. I haven't seen the improvement on on the first attempt.
> ... <100ms as well (not that it can't be better, but > this is certainly a big improvement). ... Theoretically any time bigger than 0 can be made better. On practice decreasing these 100ms would mean a lot of work and high risk of regressions. Is it worth it? These 100ms is the _total_ time taken by the UML plugin at startup. That is 3% of the best NB startup time during 5.5 release and less than 2% of 6.0 startup. If each plugin took 100ms it would result in less than 1 sec. overall NB startup :)