I guess I was thinking that the multiple iterations allow for easier
pinpointing of noise on the system. I think I remember originally
writing this during an episode where successive runs of pgbench were
yielding wildly different results, and I wound up wanting an easy way
to detect this and examine it further, so standard deviations in
smaller sets of runs seemed an easy way to do it.
With large numbers of transactions, any noise in the system would get
smoothed out. I guess I like the ability to see the incremental
behavior of the system when using pgbench, and this lets me run it
for a long enough duration inspecting more often.
If this isn't deemed generally useful functionality, that's fine.
Thomas F. O'Connell
Database Architecture and Programming
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
pgsql-patches by date
|Next:||From: Tom Lane||Date: 2006-01-25 20:46:08|
|Subject: Re: Libpq COPY optimization patch |
|Previous:||From: James William Pye||Date: 2006-01-25 19:20:38|
|Subject: Re: Adding a --quiet option to initdb|