Re: usleep feature for pgbench

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Jan Wieck <JanWieck(at)Yahoo(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: usleep feature for pgbench
Date: 2007-07-06 17:32:27
Message-ID: 468E7CAB.9070802@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jan Wieck wrote:
> On 7/6/2007 10:44 AM, Peter Eisentraut wrote:
>> Am Donnerstag, 5. Juli 2007 21:12 schrieb Jan Wieck:
>>> To test some changes in Slony I needed a
>>>
>>> \usleep [microseconds|:variable]
>>>
>>> in pgbench's scripting language to be able to have hundreds of
>>> concurrent running transactions without totally swamping the system. I
>>> was wondering if anyone would object to permanently adding this to the
>>> pgbench code?
>>
>> Or maybe a \sleep command that takes units, if it's not too much work.
>>
>
> You mean as a second, optional argument? Good idea.
>
> us = microseconds
> ms = milliseconds
> s = seconds (default)
>
> \sleep {value|:variable} [us|ms|s]
>
> Is that okay with everyone?

I won't object, but is it really worth the trouble?

Can you do microsecond precision sleeps, and on what platforms? How much
overhead is there? IIRC, on Linux the minimum time you can sleep depends
on CONFIG_HZ, and the default was 10 ms until recently.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2007-07-06 18:08:18 Re: Bgwriter strategies
Previous Message Tom Lane 2007-07-06 17:27:13 Re: BUG #3431: age() gets the days wrong