From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgbench throttling latency limit |
Date: | 2015-10-22 15:16:13 |
Message-ID: | alpine.DEB.2.10.1510221713540.22122@sto |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>> 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...
>>
>> I agree, but I'm unsure of a fix, beyond what is already done which is to
>> show units next to the figures...
>>
>> ISTM that people expect "tps" for performance, even on several seconds.
>> When it comes to skipped transactions, a count seemed more natural. I
>> really just see this as an indicator that things are not going smoothly.
>>
>> Maybe it could be shown as a percentage of scheduled transactions,
>> possibly with an option?
>>
>> A mitigation is to always run with -P 1 :-).
>
> Wouldn't printing average (per second) over the interval work?
Yes it would. That would be "skipped tps". Why not. The percentage seems
also attractive to me, because it does not matter whether you get big
figures or small figures as it is relative.
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-10-22 15:54:39 | Re: Re: [BUGS] BUG #13694: Row Level Security by-passed with CREATEUSER permission |
Previous Message | Alvaro Herrera | 2015-10-22 15:10:21 | Re: [PROPOSAL] VACUUM Progress Checker. |