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 215564 - LowPerformance took 3812 ms. in native fs IO - ZipFile.read[native]
Summary: LowPerformance took 3812 ms. in native fs IO - ZipFile.read[native]
Status: RESOLVED WONTFIX
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Infrastructure (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: Milos Kleint
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2012-07-16 05:26 UTC by KhArtNJava
Modified: 2013-05-16 06:43 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 190764

Attachments
nps snapshot (39.96 KB, application/nps)
2012-07-16 05:26 UTC, KhArtNJava 		Details
nps snapshot (40.54 KB, application/nps)
2012-10-11 05:17 UTC, Exceptions Reporter 		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 KhArtNJava 2012-07-16 05:26:39 UTC 
This bug was originally marked as duplicate of bug 204475, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE Dev (Build 201207110002)
VM: Java HotSpot(TM) Client VM, 23.1-b03, Java(TM) SE Runtime Environment, 1.7.0_05-b05
OS: Windows 7
Maximum slowness yet reported was 3812 ms, average is 3812
Comment 1 KhArtNJava 2012-07-16 05:26:44 UTC 
Created attachment 122042 [details]
nps snapshot
Comment 2 Exceptions Reporter 2012-10-11 05:17:19 UTC 
Created attachment 125745 [details]
nps snapshot
Comment 3 Milos Kleint 2013-05-16 06:43:55 UTC 
it appears the slowness is caused by slow IO during classloading, which is invoked via global lookup query. IMHO inevitable, it's a consequence of lazy loading of module system. classes get loaded on demand saving space and startup time. In case of slow IO (because of IDE startup or 3rd party app use) the loading can slow down the AWT in some cases.

closing as wontfix as there's no clear way of making sure classloading never happens on AWT thread.