-
Enhancement
-
Resolution: Fixed
-
P4
-
17, 19
-
b12
There are sometimes huge spikes in promotion, up to a few GBs; the current PLAB sizing algorithm is not meant to work well with such spiky behavior.
This leads to lots of direct allocations (some tests show ~10%) which is seems a lot of direct allocations in total (i.e. 10% of a few GBs of direct allocations is still a lot, while it does not really matter for e.g. 200MB) (random number).
Maybe decreasing the amount of direct allocations improves object copy performance in such cases; one option is to resize PLABs in such cases, or adjust the allowed direct allocations/waste.
This leads to lots of direct allocations (some tests show ~10%) which is seems a lot of direct allocations in total (i.e. 10% of a few GBs of direct allocations is still a lot, while it does not really matter for e.g. 200MB) (random number).
Maybe decreasing the amount of direct allocations improves object copy performance in such cases; one option is to resize PLABs in such cases, or adjust the allowed direct allocations/waste.
- blocks
-
-
- Resolved
-
- relates to
-
-
- Open
-
-
-
- Open
-
-
-
- Resolved
-
- links to
-
Review
openjdk/jdk/9726