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 169002 - 11s when opening javadoc Search Index
Summary: 11s when opening javadoc Search Index
Status: RESOLVED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Javadoc (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jan Pokorsky
URL: http://statistics.netbeans.org/except...
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2009-07-22 23:40 UTC by Jesse Glick
Modified: 2009-10-15 17:02 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 154016

Attachments
nps snapshot (43.18 KB, bin/nps)
2009-07-22 23:40 UTC, Jesse Glick 		Details
nps snapshot (20.07 KB, bin/nps)
2009-07-23 21:23 UTC, Jesse Glick 		Details
nps snapshot (39.09 KB, bin/nps)
2009-07-30 15:31 UTC, Jiri Prox 		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 Jesse Glick 2009-07-22 23:40:26 UTC 
Build: NetBeans IDE Dev (Build 090721)
VM: Java HotSpot(TM) Client VM, 14.0-b16, Java(TM) SE Runtime Environment, 1.6.0_14-b08
OS: Linux, 2.6.28-13-generic, i386

User Comments:
nicoliniyo: opening a xhtml file

jglick: Using internal Mozilla, trying to browse Javadoc.


Maximal alredy reported slowness was 11344 ms, average is 7767
Comment 1 Jesse Glick 2009-07-22 23:40:31 UTC 
Created attachment 85098 [details]
nps snapshot
Comment 2 Jaroslav Tulach 2009-07-23 12:18:16 UTC 
11s in Swing HTML Browser, especially when loading fonts. Will probably be obsolete (replaced by other problems) as 
soon as native browser is integrated.
Comment 3 Jesse Glick 2009-07-23 21:23:42 UTC 
Build: NetBeans IDE Dev (Build 090721)
VM: Java HotSpot(TM) Client VM, 1.5.0_18-b02, Java(TM) 2 Runtime Environment, Standard Edition, 1.5.0_18-b02
OS: Linux, 2.6.28-13-generic, i386

User Comments: 
Opened a JSP.
Maximal alredy reported slowness was 12172 ms, average is 9235
Comment 4 Jesse Glick 2009-07-23 21:23:52 UTC 
Created attachment 85149 [details]
nps snapshot
Comment 5 Jiri Prox 2009-07-30 15:31:07 UTC 
Build: NetBeans IDE Dev (Build 200907300201)
VM: Java HotSpot(TM) Client VM, 11.3-b02, Java(TM) SE Runtime Environment, 1.6.0_13-b03
OS: Linux, 2.6.24-23-generic, i386

User Comments: 
Opening javadoc index search
Maximum slowness yet reported was 12172 ms, average is 9966
Comment 6 Jiri Prox 2009-07-30 15:31:21 UTC 
Created attachment 85548 [details]
nps snapshot
Comment 7 Stanislav Aubrecht 2009-09-01 11:35:24 UTC 
the first two snapshots point to slow swing browser - nothing we can do about this
the last snapshots indicates a possible problem in implementation of
org.netbeans.api.java.queries.JavadocForBinaryQuery.findJavadoc()

reassigning to performance team for reevaluation (or close as wontfix)
Comment 8 Jaroslav Tulach 2009-09-08 12:29:59 UTC 
OK, let start with the last snapshot:
http://www.netbeans.org/nonav/issues/showattachment.cgi/85548/snapshot.nps

It shows that while opening IndexSearch (that is probably TopComponent?), the system also computes all getDocRoots(). 
That can take a long time as it involves various project queries. Please display the component, reschedule its 
initialization outside of AWT and if necessary return then back to show the results.
Comment 9 Jesse Glick 2009-09-16 01:08:11 UTC 
I'm guessing this is the wrong component and JJ has other things to do. :-)
Comment 10 Jan Pokorsky 2009-09-17 17:28:11 UTC 
It was introduced by putting the load of doc roots task out of the module warm up not to block the IDE start up due to
Menu/Javadoc References. I will fix.
Comment 11 Jan Pokorsky 2009-10-15 17:02:44 UTC 
fixed jet-main #5b83012b5d8d