From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Hackers <pgsql-hackers@postgresql.org>
Cc: pgsql-performance@postgresql.org, "Advocacy" <pgsql-advocacy@postgresql.org>
Subject: Re: [HACKERS] More benchmarking of wal_buffers
Date: Thu, 13 Feb 2003 21:29:17 -0500
Message-ID: <3331.1045189757@sss.pgh.pa.us> (raw)
In-Reply-To: <GNELIHDDFBOCMGBFGEFOKEIKCFAA.chriskl@familyhealth.com.au>
References: <GNELIHDDFBOCMGBFGEFOKEIKCFAA.chriskl@familyhealth.com.au>
"Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes:
> I've just spent the last day and a half trying to benchmark our new database
> installation to find a good value for wal_buffers. The quick answer - there
> isn't, just leave it on the default of 8.
I don't think this is based on a useful test for wal_buffers. The
wal_buffers setting only has to be large enough for the maximum amount
of WAL log data that your system emits between commits, because a commit
(from anyone) is going to flush the WAL data to disk (for everyone).
So a benchmark based on short transactions is just not going to show
any benefit to increasing the setting.
Benchmarking, say, the speed of massive COPY IN operations might show
some advantage to larger wal_buffers. Although I'm not real sure that
it'll make any difference for any single-backend test. It's really just
the case where you have concurrent transactions that all make lots of
updates before committing that's likely to show a win.
> One proof that has come out of this is that wal_buffers does not affect
> SELECT only performance in any way.
Coulda told you that without testing ;-). Read-only transactions emit
no WAL entries.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, chriskl@familyhealth.com.au, pgsql-hackers@postgresql.org, pgsql-advocacy@postgresql.org
Subject: Re: [HACKERS] More benchmarking of wal_buffers
In-Reply-To: <3331.1045189757@sss.pgh.pa.us>
References: <GNELIHDDFBOCMGBFGEFOKEIKCFAA.chriskl@familyhealth.com.au> <3331.1045189757@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