On Mon, Jul 27, 2015 at 3:19 AM, Chris Withers
wrote:
> On 24/07/2015 22:51, Jeff Janes wrote:
>
> starting vacuum...end.
>
>> transaction type: TPC-B (sort of)
>> scaling factor: 1
>>
>
> This is your problem. There is only one row in the pgbench_branch
> table, and every transaction has to
On 24/07/2015 22:51, Jeff Janes wrote:
starting vacuum...end.
transaction type: TPC-B (sort of)
scaling factor: 1
This is your problem. There is only one row in the pgbench_branch
table, and every transaction has to update that one row. This is
inherently a seriaized event.
Indeed
On Fri, Jul 24, 2015 at 12:13 PM, Chris Withers
wrote:
> On 24/07/2015 19:21, Jan Lentfer wrote:
>
>>
>> I've been doing some lightweight load testing with
“pgbench -c8 -j8 -T10”
When run locally on the postgres server I've testing, this gives
around 5000tps
When I
On 24/07/2015 19:21, Jan Lentfer wrote:
I've been doing some lightweight load testing with
“pgbench -c8 -j8 -T10”
When run locally on the postgres server I've testing, this gives
around 5000tps
When I do it from a server that has a 13ms ping latency, it drops to
37tps.
This is using the defa
>> Am 24.07.2015 um 18:59 schrieb Chris Withers :
>>
>> Hi all,
>>
>> I've been doing some lightweight load testing with
>> “pgbench -c8 -j8 -T10”
>>
>> When run locally on the postgres server I've testing, this gives around
>> 5000tps
>>
>> When I do it from a server that has a 13ms ping la
That seems to be a large drop. On the other hand 13 ms is also like a very
large network latency. On LAN your usually in the sub ms area. So going from
e.g. 0.2 ms to 13ms is 65 fold decrease. What is the network toplogy like?
Jan
Von meinem iPad gesendet
> Am 24.07.2015 um 18:59 schrieb Chris
Hi all,
I've been doing some lightweight load testing with
“pgbench -c8 -j8 -T10”
When run locally on the postgres server I've testing, this gives around
5000tps
When I do it from a server that has a 13ms ping latency, it drops to 37tps.
This is using the default pgbench script, is it to be
