JDK-8243273 : Shenandoah: untie dependency between humongous threshold and TLAB size
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Priority: P4
  • Status: Closed
  • Resolution: Not an Issue
  • Submitted: 2020-04-21
  • Updated: 2025-09-17
  • Resolved: 2025-09-17
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
Relates :  
JDK-8338444 - Shenandoah: Remove ShenandoahHumongousThreshold tunable
Description
Current Shenandoah code ties up TLAB size to be less than humongous object size. There is no particular reason why it is so: indeed, we can allocate TLAB larger than humongous object without repercussions. The only caveat is that humongous object can "hide" in the larger TLAB, which would be a UX problem.
Comments
This is not an issue ever since JDK-8338444 was integrated. Now the humongous size is capped at region size, which is also the max TLAB we can reasonably allocate. So the dependency between TLAB size and humongous threshold is no longer present.
17-09-2025
http://cr.openjdk.java.net/~shade/8243273/webrev.01/
21-04-2020