| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | "Bort, Paul" <pbort(at)tmwsystems(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Adding a pgbench run to buildfarm |
| Date: | 2006-07-25 17:59:59 |
| Message-ID: | 20060725175959.GA83250@pervasive.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Jul 23, 2006 at 11:52:14PM -0400, Bort, Paul wrote:
> -hackers,
>
> With help from Andrew Dunstan, I'm adding the ability to do a pgbench
> run after all of the other tests during a buildfarm run.
>
> Andrew said I should solicit opinions as to what parameters to use. A
> cursory search through the archives led me to pick a scaling factor of
> 10, 5 users, and 100 transactions. All of these will be adjustable using
> the build-farm.conf mechanism already in place.
Why is it being hard-coded? I think it makes a lot more sense to allow
pg_bench options to be specified in the buildfarm config. Even better
yet would be specifying them on the command line, which would allow
members to run a more rigorous test once a day/week (I'm thinking one
that might take 30 minutes, which could well ferret out some issues that
a simple 5 minute test won't).
--
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 | Tom Lane | 2006-07-25 18:02:31 | Re: Resurrecting per-page cleaner for btree |
| Previous Message | Jim C. Nasby | 2006-07-25 17:49:18 | Re: On-disk bitmap index patch |