HI, thanks for your replay, At 2013-07-26 15:17:17,"Fabien COELHO" <coe...@cri.ensmp.fr> wrote:
> >> when client thread big, the tps without connection time wrong!!!! >> number of threads: 100 >> duration: 10 s > >My 0.02 €: > >I cannot test that on my laptop! What kind of server is this? > The Server Is HP DL360. CPU E5504 2.0GHz >The thread start time is currently taken before thread creation. The >overhead of creating 100 threads compared to 10 seconds of run is quite >significant and may impact the result. The second issue is that 800 >connections and as many server processes must be created, and the time for >that must be quite significant as well against the 10 second run. > >So I would mostly classify that as a feature rather than a bug, because >the run is so short. YES, I agree with you. When testing time 100 second, the result is: http://blog.163.com/digoal@126/blog/static/163877040201362495136271/ pg93@db-172-16-3-33-> pgbench -M prepared -n -r -f ./test.sql -c 160-j 160-T 120 digoal transaction type:Custom query scaling factor:1 query mode: prepared number of clients:160 number of threads:160 duration:120 s number of transactions actually processed:28424102 tps=236795.526880(including connections establishing) tps =350493.897174(excluding connections establishing) statement latencies in milliseconds: 0.438618 select1; > >BTW, I'm planning to submit an enhancement patch to pgbench to improve > >>measurements, that will include moving the start time after the thread is > >>started, and possibly help getting more consistent figures. > >-- >Fabien. I's a pretty job, Thank you, I'm waiting. ------------------------------------------- Digoal.zhou
