From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.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: Wed, 13 Dec 2006 18:36:25 -0800
Message-ID: <200612131836.25713.josh@agliodbs.com> (raw)
In-Reply-To: <200612140104.kBE14Dx09695@momjian.us>
References: <200612140104.kBE14Dx09695@momjian.us>
Bruce,
> pgbench is designed to be a general benchmark, meanining it exercises
> all parts of the system. I am thinking just reexecuting a single SELECT
> over and over again would be a better test of the CPU optimizations.
Mostly, though, pgbench just gives the I/O system a workout. It's not a
really good general workload.
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
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: josh@agliodbs.com, bruce@momjian.us, tgl@sss.pgh.pa.us, alvherre@commandprompt.com, alex@purefiction.net, mstone+postgres@mathom.us
Subject: Re: New to PostgreSQL, performance considerations
In-Reply-To: <200612131836.25713.josh@agliodbs.com>
* 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