-
Enhancement
-
Resolution: Fixed
-
P4
-
9
-
b83
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8141928 | emb-9 | Thomas Schatzl | P4 | Resolved | Fixed | team |
Current PLAB sizing most of the time wastes way more memory than is specified by PLABWasteTargetPercent. It allows the PLABs to get way too large, so particularly at the end of the evacuation there are mainly empty regions.
Try to fix this.
Good example programs that show this are dacapo eclipse (typically 30% average waste over a run) and crm fuse (50% waste, but mostly only during mixed GC).
The latter might require splitting PLAB sizing between young and mixed gcs.
In particular the formula to calculate the next PLAB size seems to be problematic.
Try to fix this.
Good example programs that show this are dacapo eclipse (typically 30% average waste over a run) and crm fuse (50% waste, but mostly only during mixed GC).
The latter might require splitting PLAB sizing between young and mixed gcs.
In particular the formula to calculate the next PLAB size seems to be problematic.
- backported by
-
JDK-8141928 Modify PLAB sizing algorithm to waste less
- Resolved
- relates to
-
JDK-8135179 Fix conversion warning after 8067341
- Resolved
-
JDK-8158919 Investigate better TLAB sizing for large VMs in G1
- Open
-
JDK-8030849 Investigate high fragmentation/waste in some situations during allocation during GC in G1
- Open