Re: [PATCH] add --progress option to pgbench (submission 3) - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [PATCH] add --progress option to pgbench (submission 3)
Date
Msg-id alpine.DEB.2.02.1306270731230.13491@localhost6.localdomain6
Whole thread Raw
In response to Re: [PATCH] add --progress option to pgbench (submission 3)  (KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>)
Responses Re: [PATCH] add --progress option to pgbench (submission 3)  (KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>)
List 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.



pgsql-hackers by date:

Previous
From: Boszormenyi Zoltan
Date:
Subject: Error code returned by lock_timeout
Next
From: Amit Kapila
Date:
Subject: Re: Review: Patch to compute Max LSN of Data Pages