From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Dag-Erling Smørgrav <des(at)des(dot)no>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Regression tests |
Date: | 2005-05-04 14:03:32 |
Message-ID: | 17916.1115215412@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
>> Quite, but in the meantime, a good benchmark should stress the system
>> enough to cause crashes, lockups or at least incorrect results if a
>> bug is introduced in the shared memory or semaphore code, and will
>> definitely reveal any slowdowns introduced by new code, so my question
>> is: where can I find a good benchmark for PostgreSQL? Note that I
>> don't care about comparing PostgreSQL to other RDBMSes; I just want to
>> a) test PostgreSQL under high concurrent load and b) if possible,
>> measure the performance impact of a patch.
> You can use contrib/pgbench as a rather simplistic test, or you could
> try OSDB (http://osdb.sourceforge.net/)
For something a little tougher, talk to Mark Wong about using OSDL's
testbed.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2005-05-04 14:11:34 | Re: pg_locks needs a facelift |
Previous Message | Andrew Dunstan | 2005-05-04 13:25:14 | Re: pgsql-hackers@postgresql.org |