Probably no skips though, because the response time needed is below 5
*seconds*, not ms : 2 tps on 10 connections, 1 transaction every 5 seconds
for each connection.
Oops. Right. But why did this test only run 16 transactions in total
instead of 20?
Because the schedule is based on a stochastic process, transactions are
not set regularly (that would induce patterns and is not representative of
real-life load) but randomly.
The long term average is expected to converge to 2 tps, but on a short run
it may differ significantly.
--
Fabien.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
