On 2021/09/04 15:27, Fabien COELHO wrote:
Hello Fujii-san,
ISTM that the patch changes pgbench so that it can skip counting
some skipped transactions here even for realistic rates under -T.
Of course, which would happen very rarely. Is this understanding right?
Yes. The point is to get out of the scheduling loop when time has expired, as
soon it is known, instead of looping there for some possibly long time.
Thanks for checking my understanding!
+ * For very unrealistic
rates under -T, some skipped
+ * transactions are not
counted because the catchup
+ * loop is not fast
enough just to do the scheduling
+ * and counting at the
expected speed.
+ *
+ * We do not bother
with such a degenerate case.
So this comment is a bit misleading? What about updating this as follows?
------------------------------
Stop counting skipped transactions under -T as soon as the timer is exceeded.
Because otherwise it can take a very long time to count all of them especially
when quite a lot of them happen with unrealistically high rate setting in -R,
which would prevent pgbench from ending immediately. Because of this behavior,
note that there is no guarantee that all skipped transactions are counted
under -T though there is under -t. This is OK in practice because it's very
unlikely to happen with realistic setting.
------------------------------
So that behavior change by the patch would be acceptable. Is this understanding
right?
I think so.
+1
One question is; which version do we want to back-patch to?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
