Re: pgbench --latency-limit option

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tatsuo Ishii <ishii(at)postgresql(dot)org>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgbench --latency-limit option
Date: 2015-12-23 16:23:10
Message-ID: alpine.DEB.2.10.1512231714520.22350@sto
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

>> 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.


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-12-23 16:27:54 Re: pgbench --latency-limit option
Previous Message Ildus Kurbangaliev 2015-12-23 16:10:53 Re: Review: GiST support for UUIDs