Re: [PATCH] add --progress option to pgbench (submission 3)

Поиск
Список
Период
Сортировка
От Fabien COELHO
Тема Re: [PATCH] add --progress option to pgbench (submission 3)
Дата
Msg-id alpine.DEB.2.02.1306261309420.13491@localhost6.localdomain6
обсуждение исходный текст
Ответ на 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)  (KONDO Mitsumasa <kondo.mitsumasa@lab.ntt.co.jp>)
Re: [PATCH] add --progress option to pgbench (submission 3)  (Robert Haas <robertmhaas@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: Re: Improvement of checkpoint IO scheduler for stable transaction responses
Следующее
От: Andres Freund
Дата:
Сообщение: Re: PQConnectPoll, connect(2), EWOULDBLOCK and somaxconn