From: | Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
Cc: | coelho(at)cri(dot)ensmp(dot)fr, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgbench - compute & show latency consistently |
Date: | 2016-09-21 10:57:40 |
Message-ID: | CAGz5QC+ZH5KngUZBSFztKA5t6_EPvZfueo0rs_H3VFyfdZabpg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 21, 2016 at 4:05 PM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> pgbench.sgml actually already had the "latency average = ..." version in its
> example. Even before this patch, we printed it with a "=" if one of options
> that caused per-transaction timings to be measured, like --rate, was used,
> and as ":" otherwise.
>
> - Heikki
>
I'm talking about the first example in pgbench.sgml.
Typical output from <application>pgbench</application> looks like:
<screen>
transaction type: <builtin: TPC-B (sort of)>
scaling factor: 10
query mode: simple
number of clients: 10
number of threads: 1
number of transactions per client: 1000
number of transactions actually processed: 10000/10000
tps = 85.184871 (including connections establishing)
tps = 85.296346 (excluding connections establishing)
</screen>
Shouldn't we include latency average here as well and explain what it is?
--
Thanks & Regards,
Kuntal Ghosh
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Ashutosh Sharma | 2016-09-21 11:24:11 | Re: pageinspect: Hash index support |
Previous Message | Heikki Linnakangas | 2016-09-21 10:35:04 | Re: pgbench - compute & show latency consistently |