Re: BUG #13484: Performance problem with logical decoding - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #13484: Performance problem with logical decoding
Date
Msg-id 20150706204509.GD340@alap3.anarazel.de
Whole thread Raw
In response to Re: BUG #13484: Performance problem with logical decoding  (olivier.gosseaume@free.fr)
Responses Re: BUG #13484: Performance problem with logical decoding  (olivier.gosseaume@free.fr)
List pgsql-bugs
On 2015-07-06 19:29:30 +0200, olivier.gosseaume@free.fr wrote:
> To be more concise :
> - ONE transaction with 4095 operations -> consumed in 80mS
> - TEN transactions with 4095 operations each (so 40950 operations) -> 380mS (which as you said is very good -less
thanlinear growth-) 
> - ONE transaction with 4096 operations -> consumed in 4204mS (ouch ...). I confirm there are only 4096 changes in one
transaction
> - TEN transactions with 4095 operations each (so 40950 operations) -> 34998mS, ouch again

Given the third result it's unlikely, but just to make sure: Are you
sure network issues aren't a factor here? 40950 changes are about 3.8MB,
over a slow network that can take a second. Additionally psql will
display all the changes in a pager, which'll not be fast either (but
shouldn't be included in \timing's output).

Greetings,

Andres Freund

pgsql-bugs by date:

Previous
From: Andres Freund
Date:
Subject: Re: BUG #13484: Performance problem with logical decoding
Next
From: olivier.gosseaume@free.fr
Date:
Subject: Re: BUG #13484: Performance problem with logical decoding