From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgbench - compute & show latency consistently |
Date: | 2016-09-21 13:23:46 |
Message-ID: | alpine.DEB.2.20.1609211510240.1634@lancre |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello Kuntal,
> <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?
Indeed, now it seems to be always printed but the documentation did not
follow, there should be a:
latency average = 117.392 ms
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: <builtin: TPC-B (sort of)>
scaling factor: 100
query mode: simple
number of clients: 10
number of threads: 1
number of transactions per client: 1000
number of transactions actually processed: 10000/10000
latency average = 9.527 ms
tps = 1049.665115 (including connections establishing)
tps = 1049.890194 (excluding connections establishing)
Which is about 10 times better.
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Jesper Pedersen | 2016-09-21 13:30:44 | Re: pageinspect: Hash index support |
Previous Message | Robert Haas | 2016-09-21 13:23:34 | Re: Tracking wait event for latches |