From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] add --progress option to pgbench (submission 3) |
Date: | 2013-06-27 05:39:32 |
Message-ID: | alpine.DEB.2.02.1306270731230.13491@localhost6.localdomain6 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dear Mitsumasa,
> As I know, famous NoSQL benchmark program which was called YCSB is display
> latency measure. I think that TPS indicates system performance for system
> administrator, and latency indicates service performance for end user, in
> custom benchmarks.
Sure. I agree that both information are very useful.
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.
So I would like to know whether the throttling patch is committed and then
update the progress patch to take that into account.
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2013-06-27 05:46:25 | Re: Review: Patch to compute Max LSN of Data Pages |
Previous Message | Boszormenyi Zoltan | 2013-06-27 05:22:35 | Error code returned by lock_timeout |