Re: [PATCH] add --throttle option to pgbench

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] add --throttle option to pgbench
Date: 2013-04-29 17:45:18
Message-ID: alpine.DEB.2.02.1304291944460.7344@localhost6.localdomain6
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello Tom,

> I'm having a hard time understanding the use-case for this feature.
> Surely, if pgbench is throttling its transaction rate, you're going
> to just end up measuring the throttle rate.

Indeed, I do not want to measure the tps if I throttle it.

The point is to generate a continuous but not necessarily maximal load,
and to test other things under such load such as possiby cascading
replication, failover, various dump strategies, whatever.

>> I wanted that to test the impact of various load levels, and for
>> functionnal tests on my laptop which should not drain the battery.
>
> How does causing a test to take longer result in reduced battery drain?

If I test a replication setup on my laptop at maximum load, I can see the
battery draining in a few seconds by looking at the effect on the time
left widget. This remark is mostly for functional tests, not for
performance test.

If I want to test the maximum load of a setup, obviously I will not do
that on my laptop, and I will not use --throttle...

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2013-04-29 17:50:02 Re: ALTER DEFAULT PRIVILEGES FOR ROLE is broken
Previous Message Tom Lane 2013-04-29 17:25:47 Re: ALTER DEFAULT PRIVILEGES FOR ROLE is broken