public inbox for [email protected]  

help / color / mirror / Atom feed

From: Adrian Klaver <[email protected]>
To: veem v <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: IO related waits
Date: Mon, 16 Sep 2024 15:11:19 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAB+=1TWZNvMhVthJ2iKs_Q4qBzMw-v_oaSz7HbFE_P_qC5jMFA@mail.gmail.com>
References: <CAB+=1TWZNvMhVthJ2iKs_Q4qBzMw-v_oaSz7HbFE_P_qC5jMFA@mail.gmail.com>

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
[email protected]

view thread (7+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: IO related waits
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox