RFR: 8312116: GenShen: make instantaneous allocation rate triggers more timely [v29]

Kelvin Nilsen kdnilsen at openjdk.org
Tue Feb 17 23:13:39 UTC 2026


On Mon, 16 Feb 2026 23:58:30 GMT, Kelvin Nilsen <kdnilsen at openjdk.org> wrote:

>> After studying large numbers of GC logs with degenerated cycles that have resulted from "late" triggers, we propose the following general improvements:
>> 
>> 1. Track trends in GC times rather than always using the average GC time plus standard deviation.  In many situations, GC times trend upward due to, for example, increasing amounts of live data that must be marked as a workload builds up its working set of memory.
>> 2. Sample allocation rates more frequently than once every 100 ms.
>> 3. Track trends in allocation rates.  In some situations, the allocation rate trends upwards due to, for example, the start of a new phase of execution or a spike in client workload.
>> 4. When we detect acceleration of allocation rate, predict consumption of memory based on accelerated allocation rates rather than assuming constant allocation rate.
>
> Kelvin Nilsen has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Improve comments

src/hotspot/share/gc/shenandoah/shenandoah_globals.hpp line 37:

> 35:                             constraint)                                     \
> 36:                                                                             \
> 37:   product(double, ShenandoahAccelerationSamplePeriod, 0.0145, EXPERIMENTAL, \

Let's change this option to ms rather than seconds for consistency with existing parameters.

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

PR Review Comment: https://git.openjdk.org/jdk/pull/29039#discussion_r2819512306


More information about the shenandoah-dev mailing list