From: Richard Huxton <dev@archonet.com>
To: Gregory Stark <stark@enterprisedb.com>
Cc: Gaetano Mendola <mendola@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: shared_buffers performance
Date: Mon, 14 Apr 2008 12:25:45 +0100
Message-ID: <48033F39.1060004@archonet.com> (raw)
In-Reply-To: <87r6d8hfgw.fsf@oxford.xeocode.com>
References: <48032021.90704@gmail.com>
<87r6d8hfgw.fsf@oxford.xeocode.com>
Gregory Stark wrote:
> "Gaetano Mendola" <mendola@gmail.com> writes:
>
>> The following graph reports the results:
>>
>> http://img84.imageshack.us/my.php?image=totalid7.png
>
> That's a *fascinating* graph.
It is, isn't it? Thanks Gaetano.
> It seems there are basically three domains.
>
> The small domain where the database fits in shared buffers -- though actually
> this domain seems to hold until the accounts table is about 1G so maybe it's
> more that the *indexes* fit in memory. Here larger shared buffers do clearly
> win.
I think this is actually in two parts - you can see it clearly on the
red trace (64MB), less so on the green (256MB) and not at all on the
blue (512MB). Presumably the left-hand steeper straight-line decline
starts with the working-set in shared-buffers, and the "knee" is where
we're down to just indexes in shared-buffers.
With the blue I guess you just get the first part, because by the time
you're overflowing shared-buffers, you've not got enough disk-cache to
take up the slack for you.
I wonder what difference 8.3 makes to this?
--
Richard Huxton
Archonet Ltd
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: dev@archonet.com, stark@enterprisedb.com, mendola@gmail.com
Subject: Re: shared_buffers performance
In-Reply-To: <48033F39.1060004@archonet.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