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 171048 - 35s in many ZipFile.open() calls - loading from default package in JFreeChart
Summary: 35s in many ZipFile.open() calls - loading from default package in JFreeChart
Status: RESOLVED DUPLICATE of bug 171810
Alias: None
Product: platform
Classification: Unclassified
Component: Module System (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Jaroslav Tulach
URL: http://statistics.netbeans.org/except...
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2009-08-28 08:07 UTC by jmichelberger
Modified: 2011-04-13 15:37 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 157142

Attachments
nps snapshot (18.55 KB, bin/nps)
2009-08-28 08:07 UTC, jmichelberger 		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 jmichelberger 2009-08-28 08:07:33 UTC 
Build: NetBeans IDE Dev (Build nbms-and-javadoc-3812-on-090826)
VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01
OS: Windows XP, 5.1, x86
Maximum slowness yet reported was 35283 ms, average is 35283
Comment 1 jmichelberger 2009-08-28 08:07:58 UTC 
Created attachment 86765 [details]
nps snapshot
Comment 2 Jaroslav Tulach 2009-08-28 10:38:53 UTC 
The snapshot looks quite good. It contains both the "wall clock" time, as well as CPU execution time. There is a lot 
of I/O activity (subversion is running, debugging of some other debuggee is on), but the system is not overloaded, the 
snapshot can be trusted:

Samples 3011
Average 10.000181021255377
Minimum 1.322794
Maximum 51.73367
Std. deviation 2.1266891866925453

The snapshot says that JarSource.getJarFile has been called once, but the JarFile.init 24 times, and ZipFile.open() 
183 times! Can anyone explain this?
Comment 3 Jaroslav Tulach 2011-04-13 15:37:57 UTC 

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