Re: [HACKERS] Use sync commit for logical replication apply in TAPtests - Mailing list pgsql-hackers

From Petr Jelinek
Subject Re: [HACKERS] Use sync commit for logical replication apply in TAPtests
Date
Msg-id f768995b-8d60-eb73-9148-a21344f432d5@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Use sync commit for logical replication apply in TAPtests  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] Use sync commit for logical replication apply in TAPtests  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On 20/04/17 14:57, Peter Eisentraut wrote:
> On 4/18/17 22:25, Petr Jelinek wrote:
>> The commit 887227a1c changed the defaults for subscriptions to do async
>> commit. But since the tests often wait for disk flush and there is no
>> concurrent activity this has increased the amount of time needed for
>> each test. So the attached patch changes the subscriptions create in tab
>> tests to use sync commit which improves performance there (because we
>> also replicate only very few transactions in the tests).
> 
> I see only a 1.5% (1s/70s) improvement in the run time of the whole test
> suite from this.  Is that what you were expecting?
> 

Hmm, on my machine the difference is around 50% (~1m vs ~2m).

--  Petr Jelinek                  http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Stas Kelvich
Date:
Subject: Re: [HACKERS] Logical replication ApplyContext bloat
Next
From: Dilip Kumar
Date:
Subject: Re: [HACKERS] Logical replication ApplyContext bloat