On Tue, May 10, 2016 at 2:41 PM, Kevin Grittner <kgri...@gmail.com> wrote:
> http://www.postgresql.org/message-id/flat/1402267501.41111.yahoomail...@web122304.mail.ne1.yahoo.com Re-reading that thread I was reminded that I had more NUMA problems when data all landed in one memory node, as can happen with pgbench -i. Note that at scale 100 and 3000 all data would fit in one NUMA node, and very likely was all going through one CPU socket. The 2 hour warm-up might have rebalanced that to some degree or other, but as an alternative to the cpuset and NUMA patch, you could stop PostgreSQL after the initialize, discard OS cache, and start fresh before your warm-up. That should accomplish about the same thing -- to better balance the use of memory across the memory nodes and CPU sockets. On most NUMA systems you can use this command to see how much memory is in use on which nodes: numactl --hardware -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
