Re: NUMA shared memory interleaving - Mailing list pgsql-hackers

From Robert Haas
Subject Re: NUMA shared memory interleaving
Date
Msg-id CA+TgmobxuETJrJYEo9WA3FFc0D4C6mA5eaxyoUp9SVFbNZtvSQ@mail.gmail.com
Whole thread Raw
In response to NUMA shared memory interleaving  (Jakub Wartak <jakub.wartak@enterprisedb.com>)
Responses Re: NUMA shared memory interleaving
List pgsql-hackers
On Wed, Apr 16, 2025 at 5:14 AM Jakub Wartak
<jakub.wartak@enterprisedb.com> wrote:
> Normal pgbench workloads tend to be not affected, as each backend
> tends to touch just a small partition of shm (thanks to BAS
> strategies). Some remaining questions are:
> 1. How to name this GUC (numa or numa_shm_interleave) ? I prefer the
> first option, as we could potentially in future add more optimizations
> behind that GUC.

I wonder whether the GUC needs to support interleaving between a
designated set of nodes rather than only being able to do all nodes.
For example, suppose someone is pinning the processes to a certain set
of NUMA nodes; perhaps then they wouldn't want to use memory from
other nodes.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: NUMA shared memory interleaving
Next
From: Konstantin Osipov
Date:
Subject: Re: Built-in Raft replication