RFR: 8365956: GenShen: Adaptive tenuring threshold algorithm may raise threshold prematurely [v5]
Paul Hohensee
phh at openjdk.org
Wed Sep 10 22:05:58 UTC 2025
On Tue, 9 Sep 2025 22:09:02 GMT, William Kemper <wkemper at openjdk.org> wrote:
>> The adaptive tenuring algorithm has been modified to begin its evaluation of mortality rates from the current tenuring threshold. To compliment this change, objects must also now be strictly above the tenuring threshold to be promoted (instead of greater-than-or-equal).
>
> William Kemper has updated the pull request with a new target base due to a merge or a rebase. The incremental webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains 20 additional commits since the last revision:
>
> - Fix include order
> - Add missing newline
> - Fix typo
> - Merge tag 'jdk-26+14' into adaptive-tenuring-threshold
>
> Added tag jdk-26+14 for changeset ab9f70dd
> - Do not require objects to be strictly older than the tenuring threshold
> - Log updated tenuring age at info, log age table at debug
> - Be consistent when comparing tenuring threshold with ages
> - Fix windows build
> - Fix release build
> - Revert unintended change
> - ... and 10 more: https://git.openjdk.org/jdk/compare/a2c26721...0ffa89c5
Looks good from a sw engineering pov (the vast majority of the changes are that). I can't definitively say that the functionality change is the right thing, but seems reasonable. I'll go by Ramki's judgement.
-------------
Marked as reviewed by phh (Reviewer).
PR Review: https://git.openjdk.org/jdk/pull/26906#pullrequestreview-3207975609
More information about the hotspot-gc-dev
mailing list