Re: pgbench throttling latency limit

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
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: 2014-10-09 19:16:00
Message-ID: 5436DEF0.10407@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/05/2014 10:43 AM, Fabien COELHO wrote:
>
> Hello Heikki,
>
>> Here are new patches, again the first one is just refactoring, and the second
>> one contains this feature. I'm planning to commit the first one shortly, and
>> the second one later after people have had a chance to look at it.
>
> I looked at it. It looks ok, but for a few spurious spacing changes here
> and there. No big deal.
>
> I tested it, everything I tested behaved as expected, so it is ok for me.

Thanks!

I committed the refactoring patch earlier, and just went through the
second patch again. I wordsmithed the documentation and comments, and
fixed the documentation on the log format. I also fixed the logging of
skipped transactions so that the schedule lag is reported correctly for
them.

One thing bothers me with the log format. Here's an example:

> 0 81 4621 0 1412881037 912698 3005
> 0 82 6173 0 1412881037 914578 4304
> 0 83 skipped 0 1412881037 914578 5217
> 0 83 skipped 0 1412881037 914578 5099
> 0 83 4722 0 1412881037 916203 3108
> 0 84 4142 0 1412881037 918023 2333
> 0 85 2465 0 1412881037 919759 740

Note how the transaction counter is not incremented for skipped
transactions. That's understandable, since we're not including skipped
transactions in the number of transactions executed, but it means that
the skipped transactions don't have a unique ID. That's annoying.

Here's a new version of the patch. I'll sleep over it before committing,
but I think it's fine now, except maybe for the unique ID thing.

- Heikki

Attachment Content-Type Size
0002-Add-latency-limit-option-to-pgbench-2.patch text/x-diff 24.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2014-10-09 19:25:05 Re: Last Commitfest patches waiting review
Previous Message Heikki Linnakangas 2014-10-09 19:14:18 Re: Last Commitfest patches waiting review