Skip site navigation (1) Skip section navigation (2)

Re: Postgres benchmarking with pgbench

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, "ml(at)bortal(dot)de" <ml(at)bortal(dot)de>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Postgres benchmarking with pgbench
Date: 2009-03-17 05:33:12
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Mon, Mar 16, 2009 at 10:17 PM, Greg Smith <gsmith(at)gregsmith(dot)com> wrote:
> On Tue, 17 Mar 2009, Gregory Stark wrote:
>> I think pgbench is just not that great a model for real-world usage
> pgbench's default workload isn't a good model for anything.  It wasn't a
> particularly real-world test when the TPC-B it's based on was created, and
> that was way back in 1990.  And pgbench isn't even a good implementation of
> that spec (the rows are too narrow, comments about that in pgbench.c).
> At this point, the only good thing you can say about pgbench is that it's
> been a useful tool for comparing successive releases of PostgreSQL in a
> relatively fair way.  Basically, it measures what pgbench measures, and that
> has only a loose relationship with what people want a database to do.

I'd say pgbench is best in negative.  I.e it can't tell you a database
server is gonna be fast, but it can usually tell you when something's
horrifically wrong.  If I just installed a new external storage array
of some kind and I'm getting 6 tps, something is wrong somewhere.

And it's good for exercising your disk farm for a week during burn in.
 It certainly turned up a bad RAID card last fall during acceptance
testing our new servers.  Took 36 hours of pgbench to trip the bug and
cause the card to lock up.  Had one bad disk drive too that pgbench
killed of for me.

In response to

pgsql-performance by date

Next:From: Joshua D. DrakeDate: 2009-03-17 05:45:41
Subject: Re: deployment query
Previous:From: Scott MarloweDate: 2009-03-17 05:26:23
Subject: Re: deployment query

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group