JDK-8209837 : Avoid initializing ExpiringCache during bootstrap
- Type: Enhancement
- Component: core-libs
- Sub-Component: java.io
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2018-08-22
- Updated: 2018-08-30
- Resolved: 2018-08-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.
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.
| JDK 12 |
|---|
12 b09Fixed  |
Related Reports
|
Relates :
|
Description
With useCanonCache off by default, we can profit slightly from avoiding creating ExpiringCaches in the FileSystem classes by default. This avoids loading and initializing 3 classes on startup. It also seems the boolean flags read during startup can be made final, allowing JIT to optimize certain operations better.