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.
Build: NetBeans IDE Dev (Build 200908022240) VM: Java HotSpot(TM) Client VM, 1.6.0_01-b06, Java(TM) SE Runtime Environment, 1.6.0_01-b06 OS: Windows Vista, 6.0, x86 Maximum slowness yet reported was 23306 ms, average is 10589
Created attachment 86168 [details] nps snapshot
This issue already has 6 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=153605
This issue already has 8 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=153605
Build: NetBeans IDE Dev (Build nbms-and-javadoc-3738-on-090814) VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01 OS: Windows XP, 5.1, x86 User Comments: Maximum slowness yet reported was 51855 ms, average is 14492
Created attachment 86382 [details] nps snapshot
This issue already has 9 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=153605
Created attachment 87342 [details] Today I tried to make a bugreport (performance of opening big files). After opening the third big file, the scanning-Task started again. Here´s the first snapshot. The second one follows.
Created attachment 87352 [details] The second Snapshot after 2 hours Scanning projects. I killed the IDE after that.
Created attachment 87353 [details] The log-file with activated Parameter "-J-Dorg.netbeans.modules.parsing.impl.indexing.RepositoryUpdater.level=FINE".
This issue already has 20 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=153605
According to the first snapshot attached to this issue, a lot of time is spent in ServerUtilities.filterByManifest in the GF plugin. This method opens 29 jar files. Is there anything we can do to avoild opening the jar files?
Hmm... I am a bit confused... I put some timing code around calls to findByManifest... it did eat up some time: 570 ms and 586 ms... but it was never triggered by opening the project properties, so doing changes in that code is unlikely to have a positive effect on this situation. I also noticed that both call are taking place on a RequestProcessor thread... not AWT... during IDE start-up. I am going to send this back to web for further analysis. If there is plugin code that is contributing to the problem opening the Project Properties dialog, let me know... and provide a bit more info about the situation in the comment.
Jindro, could you please have a look at perf reports - they all are coming from different project types (most of them from apisupport, then web and some from j2se). I could rearrange them but perhaps you want to have a look first and amend algorithm which groups reports to take into account different project types. Jindro, I have an enhancement suggestion: would it be possible in 'AWT thread dump' view to highlight all lines whose time is higher? Or even better I would calculate percentage of time spend in single line and use that percentage to calculate background color of such a line. For example 100% may mean 0 transparency of red color and 0% may mean 100% transparency of red color and use that color as line's background. It should be possible to even do it in JavaScript. That would improve readability of 'AWT thread dump'! Thanks.
Another enhancement request - just finding the 'AWT thread dump' is not easy! I was expecting it would be a single click from http://statistics.netbeans.org/exceptions/detail.do?id=153605, but it seems to be two clicks away. Also, the second click is in the caption of the popup window, which is hard to see. And I did not expect that clicking "226306" would give me any new information when I just clicked "226306". Or is there a shorter way? Would it be possible to improve the usability, please? Thanks.
I never noticed link in the title of the popup window - it is dark blue color on black background. :-) Just click that red square with arrow next to ID number on first page. That does the trick (despite link description saying "comments"). As duplicates are different issues this is not a P2.
This issue already has 21 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=153605
I filed a separate P3 issue 172274 for the web project/GlassFish part of the problem. Most of the other (false) duplicates are coming from apisupport project, reassigning.
core-main #7b3329e42c92
Build: NetBeans IDE Dev (Build nbms-and-javadoc-3943-on-090917) VM: Java HotSpot(TM) Client VM, 16.0-b08, Java(TM) SE Runtime Environment, 1.7.0-ea-b71 OS: Windows XP, 5.1, x86 User Comments: Maximum slowness yet reported was 51855 ms, average is 10513
Created attachment 87903 [details] nps snapshot
Integrated into 'main-golden', will be available in build *200909181401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-golden/rev/7b3329e42c92 User: Richard Michalsky <rmichalsky@netbeans.org> Log: #170291: slowness when opening apisupport project customizer
Build: NetBeans IDE Dev (Build nbms-and-javadoc-4068-on-091010) VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01 OS: Windows XP, 5.1, x86 User Comments: Maximum slowness yet reported was 72278 ms, average is 12103
Created attachment 89262 [details] nps snapshot
Created attachment 92141 [details] nps snapshot
Created attachment 92142 [details] nps snapshot
Created attachment 92143 [details] nps snapshot
Created attachment 92144 [details] nps snapshot