From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
Cc: | Greg Smith <greg(at)2ndQuadrant(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] add --throttle to pgbench (submission 3) |
Date: | 2013-05-28 08:13:46 |
Message-ID: | alpine.DEB.2.02.1305281011310.12479@localhost6.localdomain6 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2013-05-28 08:38:11 | Re: [PATCH] add --throttle to pgbench (submission 3) |
Previous Message | Amit Langote | 2013-05-28 08:06:17 | Re: Logging of PAM Authentication Failure |