RFR: 8373714: Shenandoah: Register heuristic penalties following a degenerated GC [v2]

Kelvin Nilsen kdnilsen at openjdk.org
Wed Jan 7 17:38:09 UTC 2026


On Tue, 6 Jan 2026 20:46:23 GMT, William Kemper <wkemper at openjdk.org> wrote:

>> May be let the heuristics (or the policy) track progress as well, and inform the actuator (i.e. op degenerated) whether it should upgrade to a full gc. It almost feels like heuristics and policy and actuator are leaking abstractions. It feels like heuristics keep track of the model parameters and learn from sensors, and the policy consults a specific heuristic to inform actuator (i.e. actions).
>> 
>> By that model, you'd have the actuator sending the sensor information to the heuristics and asking the policy (or the heuristics, if you conflate heuristics and policy) to decide which step to take next. It would seem that evaluation of the notion of progress then moves to the policy too.
>
> @kdnilsen , what do you think about having a single method called `record_degenerated`. It's a matter of fact without conflating progress and success. I don't like having duplicated code between `record_success_degenerated` and `record_unsuccessful_degenerated`. I understand what @ysramakrishna is saying, and I agree, but I think a change like that is beyond the scope of this PR.

I like this idea.  I'll try to make that work without breaking anything...

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/28834#discussion_r2669431913


More information about the hotspot-gc-dev mailing list