-
Enhancement
-
Resolution: Fixed
-
P4
-
8-shenandoah, 11-shenandoah, 14, 15
-
b18
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8245344 | 14u-cpu | Aleksey Shipilev | P4 | Resolved | Fixed | master |
JDK-8244350 | 14.0.2 | Aleksey Shipilev | P4 | Resolved | Fixed | b05 |
We currently count the allocation by type: TLAB, GCLAB, shared allocs. All together, they should add up to the "used" space in the region. That means we can ditch one of the counters, and infer it from the already tracked "used" size.
"Shared" counter seems to be the most profitable to go: it usually means either a small allocation that does not need another small roadbump on allocation path, or the humongous allocation that does increments for every region in the humongous chain.
"Shared" counter seems to be the most profitable to go: it usually means either a small allocation that does not need another small roadbump on allocation path, or the humongous allocation that does increments for every region in the humongous chain.
- backported by
-
JDK-8244350 Shenandoah: ditch one of allocation type counters in ShenandoahHeapRegion
- Resolved
-
JDK-8245344 Shenandoah: ditch one of allocation type counters in ShenandoahHeapRegion
- Resolved
- blocks
-
JDK-8241845 Shenandoah: align ShenandoahHeapRegions to cache lines
- Resolved
-
JDK-8242114 Shenandoah: remove ShenandoahHeapRegion::reset_alloc_metadata_to_shared
- Resolved