Re: [PATCH] add --throttle to pgbench (submission 3) - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [PATCH] add --throttle to pgbench (submission 3)
Date
Msg-id alpine.DEB.2.02.1305281011310.12479@localhost6.localdomain6
Whole thread Raw
In response to Re: [PATCH] add --throttle to pgbench (submission 3)  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: [PATCH] add --throttle to pgbench (submission 3)  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
>>> The use case of the option is to be able to generate a continuous gentle
>>> load for functional tests, eg in a practice session with students or for
>>> testing features on a laptop.
>>
>> If you add this to
>> https://commitfest.postgresql.org/action/commitfest_view?id=18 I'll
>> review it next month.  I have a lot of use cases for a pgbench that
>> doesn't just run at 100% all the time.
> As do I - in particular, if time permits I'll merge this patch into my
> working copy of pgbench so I can find the steady-state transaction rate
> where BDR replication's lag is stable and doesn't increase continually.
> Right now I don't really have any way of doing that, only measuring how
> long it takes to catch up once the test run completes.

You can try to use and improve the --progress option in another patch 
submission which shows how things are going.

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Logging of PAM Authentication Failure
Next
From: Craig Ringer
Date:
Subject: Re: [PATCH] add --throttle to pgbench (submission 3)