Moving Forward with AHS for G1

[Man Cao]

> > One example is that the custom container has a custom implementation
for soft limit, and still uses cgroup memory limits as hard limit. Apps
that are "good citizens" should strive to stay below the soft limit.
> That’s exactly what the purpose of memory.high is. With cgroups v2,
memory.high is a soft limit while memory.max is a hard limit. AHS should
respect both really.

Supporting both memory.high and memory.max for AHS sounds great.
The soft limit for the custom container is only one example. The custom
container also has "strange" use cases where the actual limit is larger
than cgroup's hard memory limit.

Going back to the high level, the point is that it is impractical for
organizations such as us to change deployment environments (e.g. migrating
from custom container to standard container) in order to use AHS. A flag
such as CurrentMaxHeapSize will definitely help these use cases adopt AHS.

-Man
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20250415/b8e2f205/attachment.htm>