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 81236 - uml core module slows down startup
Summary: uml core module slows down startup
Status: VERIFIED FIXED
Alias: None
Product: uml
Classification: Unclassified
Component: General (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Viktor Lapitski
URL:
Keywords: PERFORMANCE
Depends on:
Blocks: 102410
  Show dependency tree
 
Reported: 2006-07-27 10:06 UTC by Petr Nejedly
Modified: 2007-09-14 14:32 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

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 Petr Nejedly 2006-07-27 10:06:17 UTC 
uml core's ModuleInstall "decrypts" (unlocks) one of the libraries it uses,
which is very costly operation (loads big chunk of the cryptoapi).
Given the fact that the keys are "there" and quite reachable, I see no reason
for the decryption step, which slows down the startup by ~300ms (P-M@1733MHz)
and increases the VM footprint by (otherwise unused) ~200 crypto classes.
Comment 1 Kris Richards 2007-01-04 21:07:56 UTC 
changed to p3 to adhere to Netbeans priority guidelines.
Comment 2 Marian Mirilovic 2007-01-05 08:40:32 UTC 
krichard,
I think more appropriate in this place is P2. 300ms 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)
Comment 3 Trey Spiva 2007-02-01 15:36:25 UTC 
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.
Comment 4 Trey Spiva 2007-02-01 15:43:40 UTC 
This issue was reported by our performance team, not a external user.
Comment 5 Petr Nejedly 2007-02-01 15:51:52 UTC 
I don't really understand your comment.
The slowdown is unrelated to the way the module is installed (ModuleInstall's
restore() method is called every startup, and the library have to be unlocked
every time you start using it in newly started JVM).

Once the user installs the module, every time he starts the IDE again (with the
module installed and enabled), it will waste 300ms "unlocking" the library?
Or is _this_ no longer the case?
Comment 6 Trey Spiva 2007-02-01 16:04:53 UTC 
Sorry, I did not mean to update this issue.  I was meaning to update the issue 81233.  I will update that 
issue.
Comment 7 Peter Lam 2007-03-20 23:22:42 UTC 
low use case not currently impacting our installed user base.
Comment 8 Viktor Lapitski 2007-09-10 19:22:27 UTC 
fixed. 0 at startup.
Comment 9 Petr Nejedly 2007-09-14 14:32:06 UTC 
Verified. Nice fix.