Hello Greg,
I've done some more testing with the "test" patch. I have not seen any
spike at the end of the throttled run.
The attached version 11 patch does ensure that throttle added sleeps are
not included in latency measures (-r) and that throttling is performed
right at the beginning of a transaction. There is an ugly goto to do that.
I think there is still a latent bug in the code with listen which should
be set back to 0 in other places, but this bug is already there.
--
Fabien.