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 191828

Summary:	LowPerformance took 124769 ms.
Product:	projects	Reporter:	rrohm <rrohm>
Component:	Maven	Assignee:	Antonin Nebuzelsky <anebuzelsky>
Status:	RESOLVED WORKSFORME
Severity:	normal	Keywords:	PERFORMANCE
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	155772
Attachments:	nps snapshot

Description rrohm 2010-11-11 08:02:17 UTC

Build: NetBeans IDE 6.9 (Build 201006111053)
VM: Java HotSpot(TM) Client VM, 16.3-b01, Java(TM) SE Runtime Environment, 1.6.0_20-b02
OS: SunOS

User Comments:
rrohm: I started the IDE and opened a project group. The project contains some 2000++ PHP/HTML/JS files plus hidden subversion directories. 
Project analysing began. 
(BTW, it is still running, for about 25+ minutes on a quad core machine with 8 GB RAM :-( The IDE seems to ignore the setting for disabling autoscanning in the options or it has no effect on the scan after IDE start - it is a real nuisance since it renders machines with lesser CPU power and RAM and only a single core  unusable for quarters of hours - please, please have a look on that for the next releases!) 
I opened a large XML file and performed som XSLT transforation.
I started an Ant task that should copy about 1800 files to a NFS share.
The I opened the options dialog and checked the project scanning settings. 
The IDE froze after changing to other tabs in the options dialog, I do not remember exactly wich tab.



Maximum slowness yet reported was 124769 ms, average is 63938

Comment 1 rrohm 2010-11-11 08:02:21 UTC

Created attachment 102900 [details]
nps snapshot

Comment 2 Antonin Nebuzelsky 2010-11-12 15:38:56 UTC

AWT thread is blocked in execution of an external process to get the maven version number for Options/Misc/Maven panel.

This has been fixed in 7.0. Marking as worksforme now.

BTW, the "124769 ms" snapshot is broken. It is 8kb in size and shows only 79ms of time period. But as well as the other snapshot it shows the execution mentioned above. Main cause of the execution taking so ridiculously long is most probably overall overload of the system at the moment.