From: Michael Glaesemann <grzm@seespotcode.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org, Bruce Momjian <bruce@momjian.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Alexander Staubo <alex@purefiction.net>
Cc: Michael Stone <mstone+postgres@mathom.us>
Subject: Re: New to PostgreSQL, performance considerations
Date: Thu, 14 Dec 2006 15:11:11 +0900
Message-ID: <274FEBE6-C248-482C-AC27-A0369EC9812C@seespotcode.net> (raw)
In-Reply-To: <15642.1166075096@sss.pgh.pa.us>
References: <200612140104.kBE14Dx09695@momjian.us>
<200612131836.25713.josh@agliodbs.com>
<1166065359.6494.16.camel@localhost.localdomain>
<15642.1166075096@sss.pgh.pa.us>
On Dec 14, 2006, at 14:44 , Tom Lane wrote:
> The pgbench app itself becomes the bottleneck at high transaction
> rates. Awhile back I rewrote it to improve its ability to issue
> commands concurrently, but then desisted from submitting the
> changes --- if we change the app like that, future numbers would
> be incomparable to past ones, which sort of defeats the purpose of a
> benchmark no?
At the same time, if the current pgbench isn't the tool we want to
use, is this kind of backward comparison going to hinder any move to
improve it? It sounds like there's quite a bit of room for
improvement in pg_bench, and in my opinion we should move forward to
make an improved tool, one that measures what we want to measure. And
while comparison with past results might not be possible, there
remains the possibility of rerunning the improved pgbench on previous
systems, I should think.
Michael Glaesemann
grzm seespotcode net
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: grzm@seespotcode.net, tgl@sss.pgh.pa.us, jd@commandprompt.com, josh@agliodbs.com, bruce@momjian.us, alvherre@commandprompt.com, alex@purefiction.net, mstone+postgres@mathom.us
Subject: Re: New to PostgreSQL, performance considerations
In-Reply-To: <274FEBE6-C248-482C-AC27-A0369EC9812C@seespotcode.net>
* 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