Re: pgbench: Support Multiple Simultaneous Runs (with Mean and Std. Dev.)

From: "Thomas F(dot) O'Connell" <tfo(at)sitening(dot)com>
To: PgSQL - Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: pgbench: Support Multiple Simultaneous Runs (with Mean and Std. Dev.)
Date: 2006-01-25 20:02:17
Message-ID: 6D6252E6-136D-4CFC-B1A6-E11961CC8121@sitening.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

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
Co-Founder
Sitening, LLC

http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005 (cell)
615-469-5150 (office)
615-469-5151 (fax)

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-01-25 20:46:08 Re: Libpq COPY optimization patch
Previous Message James William Pye 2006-01-25 19:20:38 Re: Adding a --quiet option to initdb