| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8141884 | emb-9 | Thomas Schatzl | P4 | Resolved | Fixed | team |
Detecting issues with PLABs, particularly about fragmentation, is currently very limited as the only information received is the current and desired PLAB size.
It would be interesting to have the following additional information:
- amount of copied data
- amount of wasted data due to losing a race when claiming an object to copy
- amount of wasted data when an object does not fit the PLAB and must be retired (inner fragmentation)
- amount of wasted data when retiring a PLAB at the end of GC (phase)
- number of refills requested
In addition to that, some statistics about the (outer) fragmentation occuring when retiring an allocation region and the number of allocation regions used.
It would be interesting to have the following additional information:
- amount of copied data
- amount of wasted data due to losing a race when claiming an object to copy
- amount of wasted data when an object does not fit the PLAB and must be retired (inner fragmentation)
- amount of wasted data when retiring a PLAB at the end of GC (phase)
- number of refills requested
In addition to that, some statistics about the (outer) fragmentation occuring when retiring an allocation region and the number of allocation regions used.
- backported by
-
JDK-8141884 Add detailed information about PLAB memory usage
-
- Resolved
-
- blocks
-
JDK-8133530 Add JFR event for evacuation statistics
-
- Resolved
-
- relates to
-
-
- Open
-
-
-
- Open
-