Postgres vs. intel ccNUMA on Linux

From: James Robinson <jlrobins(at)socialserve(dot)com>
To: Hackers Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Postgres vs. intel ccNUMA on Linux
Date: 2010-09-29 18:45:20
Message-ID: BF587806-E961-4AB8-9ED9-164F3BA55E75@socialserve.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hackers,

Any tips / conventional wisdom regarding running postgres on large-
ish memory ccNUMA intel machines, such as a 32G dual-quad-core,
showing two NUMA nodes of 16G each? I expect each postgres backend's
non-shared memory usage to remain nice and reasonably sized, hopefully
staying within the confines of its processor's local memory region,
but how will accesses to shared memory and / or buffer cache play out?
Do people tune their backends via 'numactl' ?

Furthermore, if one had more than one database being served by the
machine, would it be advisable to do this via multiple clusters
instead of a single cluster, tweaking the processor affinity of each
postmaster accordingly, trying to ensure each cluster's shared memory
segments and buffer cache pools remain local for the resulting backends?

Thanks!
----
James Robinson
Socialserve.com

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dimitri Fontaine 2010-09-29 19:09:05 Re: recovery.conf location
Previous Message Colin 't Hart 2010-09-29 18:27:11 Re: documentation udpates to pgupgrade.html