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.1306261309420.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>)
Re: [PATCH] add --progress option to pgbench (submission 3)  (Robert Haas <robertmhaas@gmail.com>)
List 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.

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Improvement of checkpoint IO scheduler for stable transaction responses
Next
From: Andres Freund
Date:
Subject: Re: PQConnectPoll, connect(2), EWOULDBLOCK and somaxconn