From: Tom Lane <tgl@sss.pgh.pa.us>
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 15:31:54 -0400
Message-ID: <21220.1208201514@sss.pgh.pa.us> (raw)
In-Reply-To: <87r6d8hfgw.fsf@oxford.xeocode.com>
References: <48032021.90704@gmail.com>
<87r6d8hfgw.fsf@oxford.xeocode.com>
Gregory Stark <stark@enterprisedb.com> writes:
> The transition domain where performance drops dramatically as the database
> starts to not fit in shared buffers but does still fit in filesystem cache.
It looks to me like the knee comes where the DB no longer fits in
filesystem cache. What's interesting is that there seems to be no
synergy at all between shared_buffers and the filesystem cache.
Ideally, very hot pages would stay in shared buffers and drop out of the
kernel cache, allowing you to use a database approximating all-of-RAM
before you hit the performance wall. It's clear that in this example
that's not happening, or at least that only a small part of shared
buffers isn't getting duplicated in filesystem cache.
Of course, that's because pgbench reads a randomly-chosen row of
"accounts" in each transaction, so that there's exactly zero locality
of access. A more realistic workload would probably have a Zipfian
distribution of account number touches, and might look a little better
on this type of test.
regards, tom lane
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: tgl@sss.pgh.pa.us, stark@enterprisedb.com, mendola@gmail.com
Subject: Re: shared_buffers performance
In-Reply-To: <21220.1208201514@sss.pgh.pa.us>
* 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