pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Brown <kevin@sysexperts.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Tuning scenarios (was Changing the default configuration)
Date: Fri, 14 Feb 2003 01:04:34 -0500
Message-ID: <4590.1045202674@sss.pgh.pa.us> (raw)
In-Reply-To: <20030214053124.GQ1833@filer>
References: <303E00EBDD07B943924382E153890E5434A909@cuthbert.rcsinc.local>
	<26004.1044980414@sss.pgh.pa.us>
	<3E492E06.2030702@postgresql.org>
	<200302110918.48614.josh@agliodbs.com>
	<26582.1044984365@sss.pgh.pa.us>
	<3E493415.9090004@postgresql.org>
	<26850.1044985975@sss.pgh.pa.us>
	<20030214053124.GQ1833@filer>

Kevin Brown <kevin@sysexperts.com> writes:
> You don't have any real confidence in pgbench.  Fair enough.  What
> *would* you have confidence in?

Measurements on your actual application?

In fairness to pgbench, most of its problems come from people running
it at tiny scale factors, where it reduces to an exercise in how many
angels can dance on the same pin (or, how many backends can contend to
update the same row).  And in that regime it runs into two or three
different Postgres limitations that might or might not have any
relevance to your real-world application --- dead-index-row references
used to be the worst, but I think probably aren't anymore in 7.3.
But those same limitations cause the results to be unstable from run
to run, which is why I don't have a lot of faith in reports of pgbench
numbers.  You need to work quite hard to get reproducible numbers out
of it.

No, I don't have a better benchmark in my pocket :-(

			regards, tom lane



view thread (10+ messages)  latest in thread

Message-ID: <4590.1045202674@sss.pgh.pa.us>
Permalink:  ../4590.1045202674@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/4590.1045202674@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, kevin@sysexperts.com
  Subject: Re: Tuning scenarios (was Changing the default configuration)
  In-Reply-To: <4590.1045202674@sss.pgh.pa.us>
  References: <303E00EBDD07B943924382E153890E5434A909@cuthbert.rcsinc.local> <26004.1044980414@sss.pgh.pa.us> <3E492E06.2030702@postgresql.org> <200302110918.48614.josh@agliodbs.com> <26582.1044984365@sss.pgh.pa.us> <3E493415.9090004@postgresql.org> <26850.1044985975@sss.pgh.pa.us> <20030214053124.GQ1833@filer> <4590.1045202674@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