On 10/22/2012 01:20 PM, Franklin, Dan (FEN) wrote:
http://blog.jcole.us/2010/09/28/mysql-swap-insanity-and-the-numa-archite cture/
Yeah, I remember reading that a while back. While interesting, it doesn't really apply to PG, in that unlike MySQL, we don't allocate any large memory segments directly to any large block. With MySQL, it's not uncommon to dedicate over 50% of RAM to the MySQL process itself, but I don't often see PG systems with more than 8GB in shared_buffers.
All the rest should be available for random allocation in general. At least, in theory.
-- Shaun Thomas OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604 312-444-8534 stho...@optionshouse.com ______________________________________________ See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
