Re: Safe vm.overcommit_ratio for Large Multi-Instance PostgreSQL Fleet - Mailing list pgsql-performance

From Frédéric Yhuel
Subject Re: Safe vm.overcommit_ratio for Large Multi-Instance PostgreSQL Fleet
Date
Msg-id 6e36e010-c93c-4d9b-a7ed-db6da1416716@dalibo.com
Whole thread Raw
In response to Re: Safe vm.overcommit_ratio for Large Multi-Instance PostgreSQL Fleet  (Frits Hoogland <frits.hoogland@gmail.com>)
Responses Re: Safe vm.overcommit_ratio for Large Multi-Instance PostgreSQL Fleet
List pgsql-performance

On 8/8/25 10:21, Frits Hoogland wrote:
> If swappiness is set to 0, but swap is available, some documentation 
> suggests it will never use anonymous memory, however I found this not to 
> be true, linux might still choose anonymous memory to reclaim.


A bug in RHEL8 meant that swappiness was not taken into account unless 
cgroupv2 was configured or vm.force_cgroup_v2_swappiness was set to 1. 
See references [1] and [2]. Could this be the cause of your observation?

[1] https://access.redhat.com/solutions/6785021
[2] https://github.com/systemd/systemd/issues/9276



pgsql-performance by date:

Previous
From: Jorge Rodriguez
Date:
Subject: Re: Safe vm.overcommit_ratio for Large Multi-Instance PostgreSQL Fleet
Next
From: Frits Hoogland
Date:
Subject: Re: Safe vm.overcommit_ratio for Large Multi-Instance PostgreSQL Fleet