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 39956 - A regression in Javadoc Manager dialog open time
Summary: A regression in Javadoc Manager dialog open time
Status: VERIFIED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Javadoc (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jan Pokorsky
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2004-02-11 13:15 UTC by Antonin Nebuzelsky
Modified: 2004-08-13 12:11 UTC (History)
0 users

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 Antonin Nebuzelsky 2004-02-11 13:15:27 UTC 
Performance test results consistently show a
regression in the time for displaying Javadoc
Manager dialog. The absolute times together with
relative percentages of comparison to NB351:

Javadoc Manager dialog open (1st invocation)
linux:    1 349 ms (+58.0%)
solaris:  1 996 ms (+64.8%)
xp:       1 156 ms (+54.1%)

Javadoc Manager dialog open (2nd and next invocs)
linux:      491 ms (+77.3%)
solaris:    821 ms (+71.9%)
xp:         328 ms (+81.2%)

My guess is that the reason might be that Javadoc
Manager now lists more javadoc mounts. But this
should not be an excuse.
Comment 1 _ tboudreau 2004-02-23 11:22:38 UTC 
Tonda, if you haven't already, you might want to check the numbers with the line switch to 
preresolve classes.  TTV uses a bunch of infrastructure from the property sheet for 
rendering.  In 3.5.1, the property sheet is on screen by default, so this will already be 
loaded; in 3.6, the user will have to open the property sheet first.  May be part of the 
problem, may not, I don't know.
Comment 2 Jan Pokorsky 2004-03-01 13:57:34 UTC 
If it is caused by increasing number of javadoc filesystems it would
help to improve responsibility by an async initialization as the
tools/options window does.
Comment 3 psuk 2004-03-01 15:10:08 UTC 
Requesting Waiver for 3.6

Justification
---------------------
It's a scalability issue, rather than pure performance problem.
The code has not been changed from NB351. The only thing that's
different from NB351 is the number of mounted javadocs after installation.

Long term solution
------------------------------------------
Rewrite the initialization of the dialog to use asynchronous reading.

It might be doable during high resistance mode, but since the fix is
not going to be trivial and there are some other important bugs that
need to be fixed for Code Freeze Milestone, we'd rather spend time on
fixing these critical bugs.
Comment 4 Jan Chalupa 2004-03-05 16:40:18 UTC 
Waiver approved.
Comment 5 psuk 2004-04-20 18:11:56 UTC 
We might get different number after merging with new buildsystem. I'll
leave it open for now and see what we'll get.
Changing target to promoD
Comment 6 _ rkubacki 2004-04-30 15:40:17 UTC 
There is no javadoc manager after build system merge. Should we close
this as fixed (or maybe invalid)?
Comment 7 Jan Pokorsky 2004-05-11 14:10:31 UTC 
Closed as WONTFIX since the manager is not part of the product any more.
Comment 8 Antonin Nebuzelsky 2004-06-11 16:58:51 UTC 
OK