public inbox for [email protected]  

help / color / mirror / Atom feed

From: Frédéric Yhuel <[email protected]>
To: Frits Hoogland <[email protected]>
Cc: Joe Conway <[email protected]>
Cc: Priya V <[email protected]>
Cc: [email protected]
Subject: Re: Safe vm.overcommit_ratio for Large Multi-Instance PostgreSQL Fleet
Date: Tue, 19 Aug 2025 19:40:10 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>



On 8/19/25 17:37, Frits Hoogland wrote:
> The specific issue I see in certain cases leading to unreasonable swap usage is Linux workingset detection kicking in

Do you have a way to highlight that precisely? I mean, can you prove 
that it is Linux workingset detection that is causing swapping? I've 
also encountered surprising cases where the swap fills up despite there 
being plenty of available memory (lots of page cache). However these 
cases were not associated with slowdowns or other problems. I only 
became aware of them because a client was anxious about her swap usage.

view thread (13+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Safe vm.overcommit_ratio for Large Multi-Instance PostgreSQL Fleet
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox