Re: [HACKERS] pgbench --latency-limit option

Hello Robert & Tatsuo, Some paraphrasing and additional comments. $ pgbench -p 11002 --rate 2 --latency-limit 1 -c 10 -T 10 test You are targetting 2 tps over 10 connections, so that is about one transaction every 5 seconds for each connection, the target is about 20 transactions in 10

Re: [HACKERS] pgbench --latency-limit option

On Wed, Dec 23, 2015 at 11:23 AM, Fabien COELHO wrote: >>> 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

Re: [HACKERS] pgbench --latency-limit option

On Tue, Dec 22, 2015 at 9:28 PM, Tatsuo Ishii wrote: > While playing with 9.5's pgbench, I faced with a strange behavior. > > $ pgbench -p 11002 --rate 2 --latency-limit 1 -c 10 -T 10 test > starting vacuum...end. > transaction type: TPC-B (sort of) > scaling factor: 1 >

Re: [HACKERS] pgbench --latency-limit option

On Wed, Dec 23, 2015 at 9:52 AM, Fabien COELHO 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 >>

Re: [HACKERS] pgbench --latency-limit option

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

Re: [HACKERS] pgbench --latency-limit option

[...] 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. Hmm.

[HACKERS] pgbench --latency-limit option

While playing with 9.5's pgbench, I faced with a strange behavior. $ pgbench -p 11002 --rate 2 --latency-limit 1 -c 10 -T 10 test starting vacuum...end. transaction type: TPC-B (sort of) scaling factor: 1 query mode: simple number of clients: 10 number of threads: 1 duration: 10 s number of