BUG #8326: pgbench tps wrong BUG

From: digoal(at)126(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #8326: pgbench tps wrong BUG
Date: 2013-07-24 01:54:34
Message-ID: E1V1oHi-0003uO-8o@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 8326
Logged by: digoal.zhou
Email address: digoal(at)126(dot)com
PostgreSQL version: Unsupported/Unknown
Operating system: CentOS 5.8 x64
Description:

when client thread big, the tps without connection time wrong!!!!
pg94(at)db-172-16-3-33-> pgbench -M prepared -n -r -f ./test.sql -T 10 -c 800
-j 100 digoal
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 800
number of threads: 100
duration: 10 s
number of transactions actually processed: 2037960
tps = 199534.267305 (including connections establishing)
tps = 675603.691013 (excluding connections establishing)
statement latencies in milliseconds:
1.019046 select 1;

when client threads small, the wrong is little.
pg94(at)db-172-16-3-33-> pgbench -M prepared -n -r -f ./test.sql -T 10 -c 800
-j 10 digoal
transaction type: Custom query
scaling factor: 1
query mode: prepared
number of clients: 800
number of threads: 10
duration: 10 s
number of transactions actually processed: 1035345
tps = 102285.117970 (including connections establishing)
tps = 115616.181725 (excluding connections establishing)
statement latencies in milliseconds:
6.812371 select 1;

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-07-24 04:22:28 Re: BUG #8274: Wildly insane boolean selectivity estimates
Previous Message Michael Paquier 2013-07-23 22:35:05 Re: BUG #8325: Missing script II