Feedback-ID: i76984098:Fastmail
Message-ID: <3dddea5e-52ab-4075-970d-a87b0c921ae7@aklaver.com>
Date: Mon, 16 Sep 2024 15:11:19 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: IO related waits
To: veem v <veema0000@gmail.com>,
 pgsql-general <pgsql-general@lists.postgresql.org>
References: <CAB+=1TWZNvMhVthJ2iKs_Q4qBzMw-v_oaSz7HbFE_P_qC5jMFA@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAB+=1TWZNvMhVthJ2iKs_Q4qBzMw-v_oaSz7HbFE_P_qC5jMFA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/3dddea5e-52ab-4075-970d-a87b0c921ae7%40aklaver.com>
Precedence: bulk

On 9/16/24 13:24, veem v wrote:
> Hi,
> One of our application using RDS postgres. In one of our streaming 
> applications(using flink) which processes 100's of millions of 
> transactions each day, we are using row by row transaction processing 
> for inserting data into the postgres database and commit is performed 
> for each row. We are seeing heavy IO:XactSynch wait events during the 
> data load and also high overall response time.
> 
> Architecture team is suggesting to enable asynch io if possible, so that 
> the streaming client will not wait for the commit confirmation from the 
> database. So I want to understand , how asynch io can be enabled and if 
> any downsides of doing this?

Are you referring to this?:

https://nightlies.apache.org/flink/flink-docs-release-1.20/docs/dev/datastream/operators/asyncio/

If not then you will need to be more specific.

> 
> Regards
> Veem

-- 
Adrian Klaver
adrian.klaver@aklaver.com