public inbox for [email protected]  

help / color / mirror / Atom feed

From: JOHN WIENCEK <[email protected]>
To: bertrand HARTWIG <[email protected]>
To: Ron Johnson <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: About asynchronous I/O
Date: Tue, 23 Jun 2026 08:04:23 -0500 (CDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CALAkhNX_6OttLJa7X+0wA7vx+wVCUMHjNcgg+2fjw=_Z3CXTKg@mail.gmail.com>
	<[email protected]>
	<CANzqJaAKAzYaGfPFLzt4ZZDs6sE5KGWuMmGWQ1oQYeC-wzHk_A@mail.gmail.com>
	<[email protected]>

Can your application assume the risk of lost transactions in the event of a database crash?
ASYNC/IO is not a good solution for all applications.


Regards

John

> On 06/23/2026 7:19 AM CDT bertrand HARTWIG <[email protected]> wrote:
>  
>  
> Very usefull on SSD AND nvme ! (low latency on IOPs). But the higher the disk latency, the greater the gains you will notice.
>  
> On SSD i observed 200%
> 
> 
> > Le 23 juin 2026 à 14:02, Ron Johnson <[email protected]> a écrit :
> > On Tue, Jun 23, 2026 at 7:26 AM bertrand HARTWIG <[email protected] mailto:[email protected]> wrote:
> > 
> > > 
> > > Hello,
> > > 
> > > The size of the database is clearly not important.
> > > 
> > > What matters are queries that are not already cached and that perform I/O.
> > > 
> > > With async I/O, you can see I/O performance improvements of up to 200%–300%. The higher the disk latency, the greater the gains you will notice.
> > > 
> >  
> > So, not so useful on SSD/NVMe?
> >  
> > 
> > > 
> > > Regards,
> > > 
> > > Bertrand
> > > 
> > > 
> > > > Le 23 juin 2026 à 09:55, ek ek <[email protected] mailto:[email protected]> a écrit :
> > > > 
> > > > Hello everyone,
> > > > Are any of you running PostgreSQL 18 on production environments sized between 1 to 3TB? Does the 'asynchronous I/O (AIO) subsystem' deliver a significant performance increase? Also, has anyone had the opportunity to benchmark it against v17?
> > > > 
> > > 
> >  
> >  
> > --
> > Death to <Redacted>, and butter sauce.
> > Don't boil me, I'm still alive.
> > <Redacted> lobster!
> > 
> 

view thread (9+ 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], [email protected]
  Subject: Re: About asynchronous I/O
  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