JDK-4747353 : Cache filename canonicalization results
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.io
  • Affected Version: 1.4.2
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-09-13
  • Updated: 2002-11-11
  • Resolved: 2002-10-25
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.4.2 mantisFixed
Related Reports
Relates :  
Relates :  
Relates :  
Description
 Investigation into traces of J2SE startup time has shown a large
fraction of time spent in filename canonicalization, in particular
redundant filename canonicalization. Some of these redundant
canonicalization operations can and should be optimized at the JDK
level; for example, redundant calls to System.loadLibrary("awt").
However, implementing a time-expiring cache at the FileSystem level
gets most if not all of the gains to be had, roughly 5% of Notepad's
startup time.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mantis FIXED IN: mantis INTEGRATED IN: mantis mantis-b05 VERIFIED IN: mantis
14-06-2004

WORK AROUND
11-06-2004

SUGGESTED FIX
11-06-2004

PUBLIC COMMENTS
10-06-2004

EVALUATION The time-expiring cache should not change the correctness properties of existing code (consider the case of file updates over NFS, which can take up to 30 seconds to propagate between machines.) Implemented in 1.4.2. ###@###.### 2002-09-13
13-09-2002