On Wed, Sep 21, 2016 at 6:53 PM, Fabien COELHO wrote:
> In front of the tps line. Well, the performance displayed could also be
> improved... On my dual core SSD laptop I just got:
>
> sh> ./pgbench -c 10 -t 1000
> starting vacuum...end.
> transaction type:
> scaling
Hello Kuntal,
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: 1/1
tps = 85.184871 (including connections establishing)
tps =
On Wed, Sep 21, 2016 at 4:05 PM, Heikki Linnakangas 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
(I just pushed the patch, didn't see your post until after that)
On 09/21/2016 01:07 PM, Kuntal Ghosh wrote:
On Thus, July 7,2016 at 08:39 PM, Fabien COELHO wrote:
Also there is still the bug under -t which displays a 0 latency.
Your patch clearly fixed the issue.
The
On 07/13/2016 11:39 AM, Fabien COELHO wrote:
number of transactions per client: 1000
-latency average = 15.844 ms
+latency average: 15.844 ms
tps = 618.764555 (including connections establishing)
I think what you have here is that colons separate input parameters and
equal signs separate
On Thus, July 7,2016 at 08:39 PM, Fabien COELHO wrote:
> Also there is still the bug under -t which displays a 0 latency.
Your patch clearly fixed the issue.
> The attached patch still fixes that and make it consistent the other way
> around, i.e. by using "=" for latency. I
Hello Peter,
number of transactions per client: 1000
-latency average = 15.844 ms
+latency average: 15.844 ms
tps = 618.764555 (including connections establishing)
I think what you have here is that colons separate input parameters and
equal signs separate result output. So I think it's
On 7/9/16 4:42 AM, Fabien COELHO wrote:
> number of transactions per client: 1000
> number of transactions actually processed: 1/1
> -latency average = 15.844 ms
> -latency stddev = 2.715 ms
> +latency average: 15.844 ms
> +latency stddev: 2.715 ms
> tps = 618.764555 (including
Currently the latency is not computed and displayed consistently:
- the computation is wrong under -t (duration is zero...)
- depending on the conditions it is shown with a ":" syntax or
a "=" syntax.
The attached minor patch makes the computation & display more consistent.
--