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 215815

Summary:	LowPerformance took 10393 ms.
Product:	projects	Reporter:	_ wadechandler <wadechandler>
Component:	Maven	Assignee:	Milos Kleint <mkleint>
Status:	RESOLVED DUPLICATE
Severity:	normal	Keywords:	PERFORMANCE
Priority:	P3
Version:	7.2
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	190935
Attachments:	nps snapshot

Description _ wadechandler 2012-07-23 02:50:40 UTC

This bug was originally marked as duplicate of bug 170858, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 7.2 (Build nbms-and-javadoc-9336-on-20120629)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.0-b21, Java(TM) SE Runtime Environment, 1.7.0_04-b20
OS: Linux

User Comments:
wadechandler: I opened the IDE. I have a good number of maven projects opened. The IDE initially was "Opening projects" for a long period of time. Said 200% of the CPU was used (4 core CPU). Then it went to "Background scanning" and the CPU usage has been between 50% and 160 or more. The CPU usage I'm reporting is only for NetBeans btw. Heavy IO can keep the application and computer from operating well in a user interface and user interaction context.



Maximum slowness yet reported was 10393 ms, average is 10393

Comment 1 _ wadechandler 2012-07-23 02:50:48 UTC

Created attachment 122255 [details]
nps snapshot

Comment 2 Milos Kleint 2012-07-23 06:44:26 UTC

from the symptoms described by wadechandler, it appears like the following problem:

with many maven projects around, when the heap memory starts to reach it's hard limit, soft references get de-referenced. Significant one for this issue is the one holding o.a.maven.MavenProject, the entire maven's model. Unfortunately in many cases we are just trading memory for CPU here, especially if project opening is still going on.

In 7.3 codebase (current dev builds) I've fixed issue 215159, bringing the memory requirements of the maven model down significantly. When just opening 300 glassfish projects we used to hit the memory ceiling as described in this issue, with the fix we're way below the limit and also significatly faster (no gc, no recreation of MavenProject objects)

if possible, please try with the latest dev builds.

*** This bug has been marked as a duplicate of bug 215159 ***