From: Paul McGarry <paul@paulmcgarry.com>
To: Ben Chobot <bench@silentmedia.com>
Cc: Postgresql Performance list <pgsql-performance@postgresql.org>
Subject: Re: shared_buffers advice
Date: Fri, 12 Mar 2010 11:19:38 +1100
Message-ID: <a056b1d41003111619v24353d5aodd1c1dfaaf0d251d@mail.gmail.com> (raw)
In-Reply-To: <8F346004-F0FB-440F-8627-0F2B8FAE53D9@silentmedia.com>
References: <a056b1d41003101822r58879e37g6c4c94ec2520290c@mail.gmail.com>
<8F346004-F0FB-440F-8627-0F2B8FAE53D9@silentmedia.com>
On 11 March 2010 16:16, Ben Chobot <bench@silentmedia.com> wrote:
> I *can* say a 10GB shared_buffer value is working "well" with my 128GB of RAM..... whether or not it's "optimal," I couldn't say without a lot of experimentation I can't afford to do right now. You might have a look at the pg_buffercache contrib module. It can tell you how utilized your shared buffers are.
Thanks Ben and Greg,
I shall start with something relatively sane (such as 10GB) and then
see how we go from there.
Once this server has brought online and bedded in I will be updating
our other three servers which are identical in hardware spec and all
have the same replicated data so I'll be able to do some real world
tests with different settings withn the same load.
(Currently one is currently running postgresql 8.1 on 32bit OS under a
VM, the other two running 8.3 on 64bit OS with 64gig of memory but
with Postgres still tuned for the 8 gigs the servers originally had
and under a VM).
Paul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: paul@paulmcgarry.com, bench@silentmedia.com
Subject: Re: shared_buffers advice
In-Reply-To: <a056b1d41003111619v24353d5aodd1c1dfaaf0d251d@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox