P4
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.
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.
- relates to
-
JDK-4760881 bad file name canonicalization causes jck and regression failures on win32
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-