From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Marc Rechté <marc4(at)rechte(dot)fr>, pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: NUMA settings |
Date: | 2020-05-05 08:00:02 |
Message-ID: | 60b780e9d34ea8a6be80193ec03ab16a160fd1eb.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, 2020-05-05 at 07:56 +0200, Marc Rechté wrote:
> Thanks for answers. Further readings make me think that we should *not*
> start postgres with numactl --interleave=all: this may have counter
> productive effect on backends anon memory (heap, stack). IMHO, what is
> important is to use Huge Pages for shared buffers: they are allocated
> (reserved) by the kernel at boot time and spread evenly on all nodes. On
> top of that they never swap.
>
> My (temp) conclusions are following:
> vm.zone_reclaim_mode = 0
> kernel.numa_balancing = 0 (still not sure with that choice)
> wm.swappiness = 60 (default)
> start postgres as usual (no numactl)
Thanks for sharing your insights.
I think that "vm.swappiness" should be 0.
PostgreSQL does its own memory management, any swapping by the kernel
would go against that.
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2020-05-05 08:08:20 | Re: Please help! Query jumps from 1s -> 4m |
Previous Message | Marc Rechté | 2020-05-05 05:56:54 | Re: NUMA settings |