From: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com> |
---|---|
To: | Florian Weimer <fweimer(at)bfk(dot)de> |
Cc: | Jesper Krogh <jesper(at)krogh(dot)cc>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Linux: more cores = less concurrency. |
Date: | 2011-04-14 11:07:24 |
Message-ID: | BANLkTikR-dvsg9tvFXAkmTXDSv4v+f27tg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
2011/4/14 Florian Weimer <fweimer(at)bfk(dot)de>:
> * Jesper Krogh:
>
>> If you have a 1 socket system, all of your data can be fetched from
>> "local" ram seen from you cpu, on a 2 socket, 50% of your accesses
>> will be "way slower", 4 socket even worse.
>
> There are non-NUMA multi-socket systems, so this doesn't apply in all
> cases. (The E5320-based system is likely non-NUMA.)
>
> Speaking about NUMA, do you know if there are some non-invasive tools
> which can be used to monitor page migration and off-node memory
> accesses?
I am unsure it is exactly what you are looking for, but linux do
provide access to counters in:
/sys/devices/system/node/node*/numastat
I also find usefull to check meminfo per node instead of via /proc
--
Cédric Villemain 2ndQuadrant
http://2ndQuadrant.fr/ PostgreSQL : Expertise, Formation et Support
From | Date | Subject | |
---|---|---|---|
Next Message | Cédric Villemain | 2011-04-14 11:29:35 | Re: Performance |
Previous Message | Florian Weimer | 2011-04-14 10:09:19 | Re: Linux: more cores = less concurrency. |