From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | veem v <veema0000(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: IO related waits |
Date: | 2024-09-16 22:11:19 |
Message-ID: | 3dddea5e-52ab-4075-970d-a87b0c921ae7@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | veem v | 2024-09-17 03:55:59 | Re: IO related waits |
Previous Message | Christophe Pettus | 2024-09-16 20:28:55 | Re: IO related waits |