Re: pgbench duration option

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgbench duration option
Date: 2008-08-18 18:25:14
Message-ID: 2216.1219083914@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg Smith <gsmith(at)gregsmith(dot)com> writes:
> On Tue, 12 Aug 2008, Tom Lane wrote:
>> This seems like a fairly bad idea, because it introduces a
>> gettimeofday() call per transaction.

> There's already lots of paths through pgbench that introduce gettimeofday
> calls all over the place. I fail to see how this is any different.

You haven't thought about it very hard then. The gettimeofday calls
that are in there are mostly at run startup and shutdown. The ones
that can occur intra-run are associated with
* the seldom-used log-each-transaction option, which pretty obviously
is a drag on performance anyway; or
* the seldom-used \sleep command, which also obviously affects pgbench's
ability to process transactions fast.

I repeat my concern that transaction rates measured with this patch will
be significantly different from those seen with the old code, and that
confusion will ensue, and that it's not hard to see how to avoid that.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2008-08-18 18:26:04 Text Selectivity Operators in String Types
Previous Message Peter Eisentraut 2008-08-18 18:17:19 Re: Compatibility types, type aliases, and distinct types