JDK-8251263 : G1: Only commit actually used space for humongous objects
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 16
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2020-08-06
  • Updated: 2020-08-07
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
tbdUnresolved
Related Reports
Blocks :  
JDK-8229373 - Reserve more than MaxHeapSize for the heap to fight humongous object fragmentation in G1
Description
One problem with humongous objects is internal fragmentation, i.e. the waste of space at the end of the object.

One option is allowing allocation into this area, another simply not committing the whole tail region, and not accounting that uncommitted space in the region budget.

Together with JDK-8229373 this could significantly improve internal fragmentation and relieve memory pressure with (many) humongous objects.

This is somewhat similar to ZGC large object handling within the regionalized heap.