| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Mitsumasa KONDO <kondo(dot)mitsumasa(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add accurate option to pgbench |
| Date: | 2013-11-02 17:21:06 |
| Message-ID: | 11889.1383412866@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:
> However I think that part of this interesting checklist and discussion
> could make it to some "caveat" section about reproducible performance
> measures in pgbench documentation, though?
+1. There's already a section of advice about how to get reproducible
numbers from pgbench --- we could certainly extend that to cover more
things.
BTW, even if we were going to put code for these things into pgbench,
driving them all off a single switch would be very bad design.
I see no reason to think that all and only these issues would be
appropriate to control for any particular user of pgbench.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-11-02 18:25:17 | gcc 4.8 compiler warning in ecpg check |
| Previous Message | Fabien COELHO | 2013-11-02 16:32:19 | Re: Add accurate option to pgbench |