Re: Wrong result with pgbench -C option? - Mailing list pgsql-patches

From Tatsuo Ishii
Subject Re: Wrong result with pgbench -C option?
Date
Msg-id 20080319.092956.119869332.t-ishii@sraoss.co.jp
Whole thread Raw
In response to Wrong result with pgbench -C option?  (Yoshiyuki Asaba <y-asaba@sraoss.co.jp>)
List pgsql-patches
Patch applied. Thanks.
--
Tatsuo Ishii
SRA OSS, Inc. Japan

> Hi,
>
> I ran pgbench with -C option. Here is an output.
>
> % pgbench -C  -c 10 -t 100  bench
> starting vacuum...end.
> transaction type: TPC-B (sort of)
> scaling factor: 1
> number of clients: 10
> number of transactions per client: 100
> number of transactions actually processed: 1000/1000
> tps = 83.209663 (including connections establishing)
> tps = 83.209663 (excluding connections establishing)
>
> The first tps was equal to the second tps. I think it is wrong because
> pgbench with -C option connects per transaction.
>
> The attached patch calculates total connection time. Here is an output
> with revised pgbench.
>
> % ./pgbench -C  -c 10 -t 100  bench
> starting vacuum...end.
> transaction type: TPC-B (sort of)
> scaling factor: 1
> number of clients: 10
> number of transactions per client: 100
> number of transactions actually processed: 1000/1000
> tps = 108.410991 (including connections establishing)
> tps = 228.657561 (excluding connections establishing)
>
> Regards,
> --
> Yoshiyuki Asaba
> y-asaba@sraoss.co.jp

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Patch to inline stable SQL set returning UDFs
Next
From: Tatsuo Ishii
Date:
Subject: Re: Patch for testing query modes on pgbench