From: Greg Smith <gsmith@gregsmith.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Brad Nicholson <bnichols@ca.afilias.info>
Cc: Kevin Kempter <kevin@consistentstate.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Monitoring buffercache...
Date: Mon, 24 Nov 2008 23:40:52 -0500 (EST)
Message-ID: <Pine.GSO.4.64.0811242335040.1084@westnet.com> (raw)
In-Reply-To: <dcc563d10811241324t116f6e71j4863632b2c0c09a5@mail.gmail.com>
References: <200811241143.57182.kevin@kevinkempterllc.com>
<dcc563d10811241146l95302b1wd0e88756883e4401@mail.gmail.com>
<1227556326.18990.98.camel@bnicholson-desktop>
<dcc563d10811241324t116f6e71j4863632b2c0c09a5@mail.gmail.com>
On Mon, 24 Nov 2008, Scott Marlowe wrote:
> My guess is that the period of time for which pg_buffercache takes locks
> on the buffer map are short enough that it isn't a real big deal on a
> fast enough server.
As the server involved gets faster, the amount of time the locks are
typically held for drops.
As your shared_buffers allocation increases, that amount of time goes up.
So how painful the overhead is depends on how fast your CPU is relative to
how much memory is in it. Since faster systems tend to have more RAM in
them, too, it's hard to say whether the impact will be noticable.
Also, noting that the average case isn't impacted much isn't the concern
here. The problem is how much having all partition locks held will
increase impact worst-case latency.
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
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: gsmith@gregsmith.com, scott.marlowe@gmail.com, bnichols@ca.afilias.info, kevin@consistentstate.com
Subject: Re: Monitoring buffercache...
In-Reply-To: <Pine.GSO.4.64.0811242335040.1084@westnet.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