| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | 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 16:32:19 |
| Message-ID: | alpine.DEB.2.02.1311021728210.18210@sto |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> Logic of this option is under following.
>> 1. execute cluster command to sort records.
>> 2. execute checkpoint to clear dirty-buffers in shared_buffers.
>> 3. execute sync command to clear dirty-file-caches in OS.
>> 4. waiting 10 seconds for raid cache is until empty .
>> 5. execute checkpoint to init checkpoint_timeout and checkpoint_segments.
>> 6. start benchmark.
>
> I have similar logic in some of my benchmarking scripts but I don't
> see a compelling reason to include it in pgbench itself.
I agree that this looks more like script material.
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?
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-11-02 17:21:06 | Re: Add accurate option to pgbench |
| Previous Message | Sawada Masahiko | 2013-11-02 15:25:33 | Re: Patch for fail-back without fresh backup |