| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Alexander Staubo <alex(at)purefiction(dot)net>, Michael Stone <mstone+postgres(at)mathom(dot)us> |
| Subject: | Re: New to PostgreSQL, performance considerations |
| Date: | 2006-12-14 03:02:39 |
| Message-ID: | 1166065359.6494.16.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, 2006-12-13 at 18:36 -0800, Josh Berkus wrote:
> 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.
It also will not utilize all cpus on a many cpu machine. We recently
found that the only way to *really* test with pgbench was to actually
run 4+ copies of pgbench at the same time.
J
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-12-14 05:44:56 | Re: New to PostgreSQL, performance considerations |
| Previous Message | Josh Berkus | 2006-12-14 02:36:25 | Re: New to PostgreSQL, performance considerations |