Re: [PATCH] pgbench --throttle (submission 7 - with lag measurement)

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Greg Smith <greg(at)2ndQuadrant(dot)com>
Cc: Tatsuo Ishii <ishii(at)postgresql(dot)org>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] pgbench --throttle (submission 7 - with lag measurement)
Date: 2013-07-22 16:43:41
Message-ID: alpine.DEB.2.02.1307221831340.7300@localhost6.localdomain6
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello Greg,

Thanks for the improvement!

I have a small reservation about "finish/end time schedule" in the second
paragraph, or maybe there is something that I do not understand. There is
no schedule for finishing anything, only start times are scheduled, so I
wish the text could avoid suggesting that finish time are scheduled.

> The rate is targeted by starting transactions along a
> Poisson-distributed schedule time line. The expected

> finish time schedule

-> start time schedule

> moves forward based on when the client first started, not when
> the previous transaction ended.

> That approach means that when transactions go past their original
> scheduled end time, it is possible for later ones to catch up again.

-> That approach means that long transactions can result in later
transactions to be late with respect to the schedule, while short
transactions makes it possible for late ones to catch up again.

Would you be ok with that?

--
Fabien.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2013-07-22 16:44:17 Re: [PATCH] pgbench --throttle (submission 7 - with lag measurement)
Previous Message Jeff Janes 2013-07-22 16:20:10 Re: Insert result does not match record count