pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Neil Conway <neilc@samurai.com>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: pgsql-performance@postgresql.org
Cc: pgsql-advocacy@postgresql.org
Subject: Re: [HACKERS] More benchmarking of wal_buffers
Date: 13 Feb 2003 01:17:52 -0500
Message-ID: <1045117072.16760.7.camel@tokyo> (raw)
In-Reply-To: <GNELIHDDFBOCMGBFGEFOKEIKCFAA.chriskl@familyhealth.com.au>
References: <GNELIHDDFBOCMGBFGEFOKEIKCFAA.chriskl@familyhealth.com.au>

On Thu, 2003-02-13 at 00:16, Christopher Kings-Lynne wrote:
> Even if you look at the attached charts and you think that 128 buffers are
> better than 8, think again - there's nothing in it.  Next time I run that
> benchmark it could be the same, lower or higher.  And the difference between
> the worst and best results is less than 3 TPS - ie. nothing.

One could conclude that this a result of the irrelevancy of wal_buffers;
another possible conclusion is that the testing tool (pgbench) is not a
particularly good database benchmark, as it tends to be very difficult
to use it to reproduceable results. Alternatively, it's possible that
the limited set of test-cases you've used doesn't happen to include any
circumstances in which wal_buffers is useful.

We definitely need some better benchmarking tools for PostgreSQL (and
no, OSDB does not cut it, IMHO). I've been thinking of taking a look at
improving this, but I can't promise I'll get the time or inclination to
actually do anything about it :-)

Cheers,

Neil
-- 
Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC






view thread (12+ messages)  latest in thread

Message-ID: <1045117072.16760.7.camel@tokyo>
Permalink:  ../1045117072.16760.7.camel@tokyo/
Also on:    postgresql.org/message-id/1045117072.16760.7.camel@tokyo

 · 

reply

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: neilc@samurai.com, chriskl@familyhealth.com.au, pgsql-hackers@postgresql.org, pgsql-advocacy@postgresql.org
  Subject: Re: [HACKERS] More benchmarking of wal_buffers
  In-Reply-To: <1045117072.16760.7.camel@tokyo>
  References: <GNELIHDDFBOCMGBFGEFOKEIKCFAA.chriskl@familyhealth.com.au> <1045117072.16760.7.camel@tokyo>

* 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