| From: | KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] add --progress option to pgbench (submission 3) |
| Date: | 2013-06-27 07:05:43 |
| Message-ID: | 51CBE447.9040409@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Febien
(2013/06/27 14:39), Fabien COELHO wrote:
> If I show a latency at full load, that would be "nclients/tps", not "1/tps".
> However, I'm hoping to pass the throttling patch to pgbench, in which case the
> latency to show is a little bit different because the "nclients/tps" would
> include sleep time and does not correspond to the latency for the end user. Also,
> under throttling it would also be useful to show the "time lag" behind scheduled
> transactions.
All right. Of Corse, I consider your wishing functions is realized with best
implementation.
> So I would like to know whether the throttling patch is committed and then update
> the progress patch to take that into account.
OK! I watch it and use it.
Best regards,
--
Mitsumasa KONDO
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2013-06-27 07:07:31 | Re: pg_filedump 9.3: checksums (and a few other fixes) |
| Previous Message | Andres Freund | 2013-06-27 06:48:28 | Re: pg_filedump 9.3: checksums (and a few other fixes) |