From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | NikhilS <nikkhils(at)gmail(dot)com> |
Cc: | "Greg Smith" <gsmith(at)gregsmith(dot)com>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: New features for pgbench |
Date: | 2007-02-13 06:45:59 |
Message-ID: | 24244.1171349159@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
NikhilS <nikkhils(at)gmail(dot)com> writes:
> As long as we use the same postgresql.conf, same hardware environment and
> exactly same parameter pgbench runs, the difference in the TPS values
> observed between the 2 sources should be a good enough indicator as to the
> viability of the new code, dont you think?
pgbench has a long-standing, thoroughly earned reputation for producing
unrepeatable results. While I agree that we shouldn't whack it around
without good cause, there's definitely some problems there, and I think
Greg is on to at least one of 'em. The question is what's the best way
to fix it ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2007-02-13 08:34:50 | Re: New features for pgbench |
Previous Message | NikhilS | 2007-02-13 06:27:27 | Re: New features for pgbench |