From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] add --throttle option to pgbench |
Date: | 2013-04-29 15:27:00 |
Message-ID: | 3113.1367249220@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:
> Please find attached a small patch to add a throttling capability to
> pgbench, that is pgbench aims at a given client transaction rate instead
> of maximizing the load. The throttling relies on Poisson-distributed
> delays inserted after each transaction.
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.
> 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?
You still need the same number of transactions if you want an honest
test, so it seems to me the machine would have to be on longer and thus
you'd eat *more* battery to get an equivalently trustworthy result.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Misa Simic | 2013-04-29 16:42:49 | Re: Graph datatype addition |
Previous Message | Atri Sharma | 2013-04-29 14:53:58 | Re: Graph datatype addition |