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.
Summary: | [68cat][69cat] AWT thread blocked for 16176 ms. | ||
---|---|---|---|
Product: | javaee | Reporter: | Chiana |
Component: | EJB | Assignee: | issues@javaee <issues> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | alcmontejo, gorrus, gtg, hmichel, indiana, jocke, jpleed3, kganfield, marfous, misterm, stopd, szmitek, thonyfd |
Priority: | P3 | Keywords: | PERFORMANCE |
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 162500 |
Attachments: | nps snapshot |
Description
Chiana
2009-11-22 15:35:46 UTC
Created attachment 91491 [details]
nps snapshot
EjbContainerChildren.createNodes() takes ~8s There are many unrelated snapshots. I evaluated newer ones (also almost one year old)... snapshot-361419.nps - java.io.WinNTFileSystem actions really slow (more than 1 second for getting LastModifiedTime - not nb sources related snapshot-355492.nps - java.io.WinNTFileSystem.* [native] took again about 99% time of all invocations, seems to be JDK/system/fs related troubles (one filesystem action takes ~12 seconds) snapshot-348173.nps - duplicate of debugger issue #169739 snapshot-343295.nps - duplicate of javaee.ejb issue #168696 Closing as duplicate of #173491 beacause the firts snapshot and the comment here from t_h are related to it: snapshot-177385.nps. *** This bug has been marked as a duplicate of bug 173491 *** isn't it okay for filesystem to be slow? I believe that bug is that potentially slow file system operations are performed in EDT? generally agree... - snapshot-355492 is opening context menu on project which took ~15s because just the reading of some bundle information takes ~9s - it's not place for asynchronous call, user has to wait for context menu. But this action is usually quick so I would expect underlaying performance troubles there - for snapshot-361419 was raised issue in visualweb component: #197402 |