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-26 11:16:41 |
Message-ID: | alpine.DEB.2.02.1306261309420.13491@localhost6.localdomain6 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dear Matsumasa,
Here is a v4 that takes into account most of your points: The report is
performed for all threads by thread 0, however --progress is not supported
under thread fork emulation if there are more than one thread. The report
time does not slip anymore.
However I've kept the format scarse. It is a style thing:-) and it is more
consistent with the kind of format used in the log. I have not added the
"latency" measure because it is redundant with the tps, and the latency
that people are expecting is the actual latency of each transactions, not
the apparent latency of transactions running in parallel, which is really
a throuput.
--
Fabien.
Attachment | Content-Type | Size |
---|---|---|
pgbench-progress-v4.patch | text/x-diff | 5.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2013-06-26 11:22:58 | Re: PQConnectPoll, connect(2), EWOULDBLOCK and somaxconn |
Previous Message | Heikki Linnakangas | 2013-06-26 11:15:59 | Re: Improvement of checkpoint IO scheduler for stable transaction responses |