-
Enhancement
-
Resolution: Fixed
-
P4
-
8-shenandoah, 11-shenandoah, 14, 15
-
b16
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8243264 | 14.0.2 | Aleksey Shipilev | P4 | Resolved | Fixed | b04 |
Deeper testing of JDK-8241139 shows that GCLockerWithShenandoah.java reliably fails in release, and always with aggressive heuristics. Investigation shows that application manages to outpace the GC every time, and then fail with OOMe too early. We should consider keep pacing enabled even in aggressive mode. This is the day 1 issue with pacing implementation.
- backported by
-
JDK-8243264 Shenandoah: avoid disabling pacing with "aggressive"
-
- Resolved
-
- blocks
-
JDK-8241139 Shenandoah: distribute mark-compact work exactly to minimize fragmentation
-
- Resolved
-