-
Bug
-
Resolution: Fixed
-
P2
-
19, 20
-
b12
-
Not verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8293727 | 19.0.2 | Thomas Schatzl | P2 | Resolved | Fixed | b01 |
JDK-8293421 | 19.0.1 | Thomas Schatzl | P2 | Closed | Fixed | b10 |
This causes significantly increased memory usage in some benchmarks; it would have been better to change the specification according to the implementation.
In one extreme example, BigRAMTester, this causes a 30% peak-to-peak remembered set memory usage regression, see attached graph.
This graph shows jdk18 remembered set memory usage in green and jdk19 remembered set memory usage in yellow.
Total memory G1 GC usage rose from 1.2GB to 1.3GB (~+8.5%).
This issue can be mitigated by setting `G1RemSetArrayOfCardsEntries` to the previous value (twice the current value for a given region size).
- backported by
-
JDK-8293727 G1 remembered set memory footprint regression after JDK-8286115
- Resolved
-
JDK-8293421 G1 remembered set memory footprint regression after JDK-8286115
- Closed
- relates to
-
JDK-8286115 G1: G1RemSetArrayOfCardsEntriesBase off-by-one error
- Resolved
- links to
-
Commit openjdk/jdk19u/673f61ba
-
Commit openjdk/jdk/8a45abd5
-
Review openjdk/jdk19u/18
-
Review openjdk/jdk/9966
(2 links to)
There are no Sub-Tasks for this issue.