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 223885 - org.netbeans.modules.versioning.util.PlaceholderPanel.addImpl: LowPerformance took 9515 ms.
Summary: org.netbeans.modules.versioning.util.PlaceholderPanel.addImpl: LowPerformance...
Status: RESOLVED WORKSFORME
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2012-12-15 21:26 UTC by szmitek
Modified: 2012-12-18 15:02 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 196616

Attachments
nps snapshot (19.95 KB, application/nps)
2012-12-15 21:26 UTC, szmitek 		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 szmitek 2012-12-15 21:26:53 UTC 
This issue was reported manually by szmitek.
It already has 1 duplicates 


Build: NetBeans IDE 7.3 Beta 2 (Build 201211062253)
VM: Java HotSpot(TM) 64-Bit Server VM, 21.0-b17, Java(TM) SE Runtime Environment, 1.7.0-b147
OS: Linux

User Comments:
szmitek: Click "Compile" on MPIVersion.cpp and Makefile in C++ Project in "Projects" tab



Maximum slowness yet reported was 9515 ms, average is 9515
Comment 1 szmitek 2012-12-15 21:26:55 UTC 
Created attachment 129415 [details]
nps snapshot
Comment 2 Ondrej Vrabec 2012-12-17 09:07:58 UTC 
Seems to be stuck in JDK native calls, i cannot find any NB code that could block the EDT. However the messages.log contains these msgs:
> WARNING [org.netbeans.JarClassLoader]: Opening /usr/local/netbeans-7.3beta2/java/modules/org-netbeans-modules-java-api-common.jar took 205 807 ms
> WARNING [org.netbeans.core.TimableEventQueue]: too much time in AWT thread org.netbeans.modules.sampler.InternalSampler@618678ff
> WARNING [org.netbeans.core.TimableEventQueue]: no snapshot taken
So maybe it is an overall OS congestion? Passing to the performance team, could you take a look at the snapshot?
Comment 3 Petr Cyhelsky 2012-12-18 15:02:20 UTC 
for the whole slowness time awt is waiting for lock held by AWT-XAWT thread which is runnable and is trying to get some window property (sun.awt.X11.XlibWrapper.XGetWindowProperty(Native Method)) It really seems that the OS is congested and some banal native function takes way too much time. As another hint of congestion the indexing of some jars took extremely long:

INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Indexing of: /usr/share/egroupware took: 221 995 ms (New or modified files: 218, Deleted files: 0) [Adding listeners took: 25 858 ms]
INFO [org.netbeans.modules.parsing.impl.indexing.RepositoryUpdater]: Complete indexing of 3 source roots took: 227 518 ms (New or modified files: 218, Deleted files: 0) [Adding listeners took: 25 914 ms]  

resolving as worksforme