RE: Proposal: Filter irrelevant change before reassemble transactions during logical decoding - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: Proposal: Filter irrelevant change before reassemble transactions during logical decoding
Date
Msg-id OSCPR01MB14966EA00C140647F2B3C1735F5C42@OSCPR01MB14966.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Proposal: Filter irrelevant change before reassemble transactions during logical decoding  (Ajin Cherian <itsajin@gmail.com>)
Responses Re: Proposal: Filter irrelevant change before reassemble transactions during logical decoding
List pgsql-hackers
Dear Ajin,

> I compared the patch 1 which does not employ a hash cache and has the
> overhead of starting a transaction every time the filter is checked.
> 
> I created a test setup of 10 million inserts in 3 different scenarios:
> 1. All inserts on unpublished tables
> 2. Half of the inserts on unpublished table and half on pupblished table
> 3. All inserts on published tables.
> 
> The percentage improvement in the new optimized patch compared to the
> old patch is:
> 
> No transactions in publication: 85.39% improvement
> Half transactions in publication: 72.70% improvement
> All transactions in publication: 48.47% improvement
> 
> Attaching a graph to show the difference.

I could not find any comparisons with HEAD. Can you clarify the throughput/latency/memory
usage with HEAD?

Best regards,
Hayato Kuroda
FUJITSU LIMITED


pgsql-hackers by date:

Previous
From: Abhishek Chanda
Date:
Subject: Re: Adding support for SSLKEYLOGFILE in the frontend
Next
From: Thomas Munro
Date:
Subject: Re: Commitfest app release on Feb 17 with many improvements