RFR: 8322484: 22-b26 Regression in J2dBench-bimg_misc-G1 (and more) on Windows-x64 and macOS-x64
Thomas Schatzl
tschatzl at openjdk.org
Thu Jan 25 16:09:36 UTC 2024
On Thu, 25 Jan 2024 15:07:15 GMT, Kim Barrett <kbarrett at openjdk.org> wrote:
>> Hi all,
>>
>> please review this improvement to managing region pin counts in g1.
>>
>> Some applications do millions of `Get/ReleasePrimitiveArrayCritical` operations per second, in particular some of the j2dbench benchmarks (e.g. vimg_copyarea 10M/s), on some platforms. Every pin/unpin results in an atomic operation that is the cause for these slowdown.
>>
>> Only Windows seems to be significantly affected.
>>
>> This suggested change implements a per-region thread local cache storing the current pin/unpin refcount difference, writing it back only when a thread pins/unpin an object in a different region.
>>
>> For these benchmarks this often reduces the amount of atomic operations to none, or a few handful; the worst improvement I have seen is that effective atomic operations were reduced to 1/10th. Overall all the j2dbench benchmark scores improve.
>>
>> There is a remaining issue with the `vimg_shapes_gradient` J2dbench subbenchmark: comparing the original results (before integration of region pinning) with latest jdk23 results, there is a regression of about 5%; this is caused by the backout of a bad compiler change (https://bugs.openjdk.org/browse/JDK-8322985). This will be fixed by its redo CR https://bugs.openjdk.org/browse/JDK-8323116.
>>
>> Testing: tier1-3, j2dbench, dacapo, specj*, renaissance benchmarks
>>
>> Thanks,
>> Thomas
>
> src/hotspot/share/gc/g1/g1RegionPinCache.inline.hpp line 42:
>
>> 40: inline void G1RegionPinCache::dec_count(uint region_idx) {
>> 41: if (region_idx == _region_idx) {
>> 42: --_count;
>
> I think _count should never underflow here. Consider adding an assertion.
I think you are correct if you change the default value of the region idx to `HRM_REGION_IDX`. Let me try this.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/17552#discussion_r1466597985
More information about the hotspot-gc-dev
mailing list