JDK-8184765 : Dynamically resize SystemDictionary
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 10
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2017-07-17
- Updated: 2020-11-13
- Resolved: 2017-11-02
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 10 |
|---|
10 b33Fixed  |
Related Reports
|
Blocks :
|
|
|
CSR :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
We should revisit the change to dynamically resize hashtables in the JVM. We didn't measure any performance improvements when first implemented with a global SystemDictionary, but with the Dictionary per ClassLoaderData change, this would save footprint and performance if the default size of dictionaries are incorrect. There may not be fixed size for each class loader, and there is not really a nice way to specify predicted loaded class count per class loader.