From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Rukh Meski <rukh(dot)meski(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>, gregsmithpgsql(at)gmail(dot)com, jan(at)wi3ck(dot)info |
Subject: | Re: pgbench throttling latency limit |
Date: | 2015-10-20 19:25:12 |
Message-ID: | 20151020192512.GB32218@awork2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2015-10-20 20:55:46 +0200, Andres Freund wrote:
> On 2014-08-14 15:01:53 +0200, Fabien COELHO wrote:
> >
> > Add --limit to limit latency under throttling
> >
> > Under throttling, transactions are scheduled for execution at certain times.
> > Transactions may be far behind schedule and the system may catch up with the
> > load later. This option allows to change this behavior by skipping
> > transactions which are too far behind schedule, and count those as skipped.
> >
> > The idea is to help simulate a latency-constrained environment such as a
> > database used by a web server.
>
> I was just trying to run tests with this, but as far as I can see it
> doesn't really work:
>
> pgbench postgres -M prepared -c 72 -j 72 -P 5 -T 3600 -R40000 -L100
> progress: 365.0 s, 18392.1 tps, lat 94.857 ms stddev 23.917, lag 90.980 ms, 106244 skipped
>
> 100k skipped transactions at a rate limit of 40k? That doesn't seem right.
Argh. It's just because I used -P5. It's a bit confusing that the other
options are per second, and this is per interval...
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-10-20 20:05:12 | Re: bugs and bug tracking |
Previous Message | Tom Lane | 2015-10-20 19:11:53 | Re: Multi-column distinctness. |