JDK-8076480 : Use all possible Metachunk sizes before expanding Metaspaces.
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P4
  • Status: Resolved
  • Resolution: Duplicate
  • Submitted: 2015-04-01
  • Updated: 2020-09-24
  • Resolved: 2020-09-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
tbdResolved
Related Reports
Duplicate :  
Description
Metaspace allocation tries to optimize the space wastage by allocating large Metachunks after allocating some number of smaller Metachunks.  The thinking is that smaller Metachunks has more wastage and if the Class has allocated several smaller Metachunks, it's a large Class so will need more space and larger Metachunks might be more optimal.

The first part of this task is to see how true the assumption: that once several smaller Metachunks have been allocated, then larger Metachunks should be allocated.

The second part of this is to change allocation so that if the desired Metachunk size is not available, choose an available Metachunk size that is big enough rather than expand the Metaspaces.
Comments
Moot after JEP387
24-09-2020

Could you take a look if this is still needed after you Metaspace rewrite?
24-09-2020