| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
| Cc: | "Bort, Paul" <pbort(at)tmwsystems(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Google SoC--Idea Request |
| Date: | 2006-04-25 15:09:10 |
| Message-ID: | 20060425150910.GF97354@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 25, 2006 at 08:39:57AM -0400, Jonah H. Harris wrote:
> On 4/25/06, Bort, Paul <pbort(at)tmwsystems(dot)com> wrote:
> > Maybe the SoC project here is just such a tuning advisor tool? Something
> > that can run pgbench repeatedly, try different settings, and compare
> > results.
>
> IIRC, that already exists. I think it was called pg_autotune or
> something similar.
Last time I tried autotune I couldn't get it to work on FreeBSD, and it
tuned a minimum of parameters. For example, it didn't touch
checkpoint_segments, which is pretty essential to tune on a higher-end
server.
Not saying it wouldn't be a good place to start, but I also don't think
it's a replacement for a built-in tuning tool.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gevik Babakhani | 2006-04-25 15:12:18 | Re: TODO Item: ACL_CONNECT |
| Previous Message | Tom Lane | 2006-04-25 14:58:05 | Re: [GENERAL] Concurrency problem building indexes |