From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Justin Clift <justin(at)postgresql(dot)org> |
Cc: | PostgreSQL General Mailing List <pgsql-general(at)postgresql(dot)org>, PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New PostgreSQL Tool available : pg_autotune |
Date: | 2002-09-22 15:30:29 |
Message-ID: | 9522.1032708629@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Justin Clift <justin(at)postgresql(dot)org> writes:
> Have been putting together a tool called "pg_autotune" for automatically
> tuning a PostgreSQL database (either local or remote). It does this by
> repetitively benchmarking PostgreSQL (using Tatsuo's pgbench code) with
> different buffer settings, then fine tuning those settings depending on
> the results returned.
You should have chosen a better foundation. pg_bench is notorious for
producing results that are (a) nonrepeatable and (b) not relevant to
a wide variety of situations. All it really tells you about is the
efficiency of a large number of updates to a small number of rows.
I'd take the results with a large grain of salt.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | am | 2002-09-22 15:53:25 | output format for dates |
Previous Message | Shridhar Daithankar | 2002-09-22 15:11:31 | Gborg projects |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2002-09-22 15:42:30 | Schema vs Namespace |
Previous Message | Shridhar Daithankar | 2002-09-22 15:11:31 | Gborg projects |