JDK-4218006 : indexing rt.jar costs 400 K
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 1.2.0
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_nt
  • CPU: x86
  • Submitted: 1999-03-07
  • Updated: 2013-11-01
  • Resolved: 1999-04-24
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.3.0 betaFixed
Related Reports
Relates :  
JDK-4770745 - Iterating over ZipFile entries is very slow when using network file systems
Description
During startup when we load and index rt.jar it costs us around 424 K 
of footprint.

This is a pretty big chunk of change.  We need to cut this down.

graham.hamilton@Eng 1999-03-07
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: kestrel kestrel-beta FIXED IN: kestrel-beta INTEGRATED IN: kestrel-beta
14-06-2004
EVALUATION OK, I have a fix where I build a much more compact index. With Cricket this saves 320 K off startup footprint and doesn't seem to impact startup time. The changes are too large and risky for Cricket. However I would like to propose this for Kestrel. graham.hamilton@Eng 1999-03-07 There is a longer description of the proposed fix at: http://zebadee/kgh/perf/zip.html graham.hamilton@Eng 1999-03-11
07-03-1999