Re: pgbench --latency-limit option

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
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 15:44:39
Message-ID: CA+TgmoaOTopo74O7UkvJE6uyJknj3jApZ27cj+6r9g09N-LDDQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 23, 2015 at 9:52 AM, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
>> In your example, you've got 10 connections and are trying to run at 2
>> tps, so to avoid having to start skipping things you need transaction
>> response times to be <~ 5 ms. The actual response time is ~5.5ms, so
>> if you ran the test for longer I think you would see some skips.
>
> 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?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-12-23 15:46:22 Re: [PROPOSAL] Backup and recovery of pg_statistic
Previous Message Tom Lane 2015-12-23 15:37:18 Re: pg_hba_lookup function to get all matching pg_hba.conf entries