public inbox for [email protected]
help / color / mirror / Atom feedFrom: Peter Geoghegan <[email protected]>
To: Andres Freund <[email protected]>
Cc: [email protected]
Cc: Tomas Vondra <[email protected]>
Cc: Thomas Munro <[email protected]>
Subject: Re: Don't synchronously wait for already-in-progress IO in read stream
Date: Sun, 9 Nov 2025 14:51:08 -0500
Message-ID: <CAH2-Wz=3_pmjM4=GLG+D2T=4uGm9dSMWbDTNzhHY3=kLoPPhaw@mail.gmail.com> (raw)
In-Reply-To: <zljergweqti7x67lg5ije2rzjusie37nslsnkjkkby4laqqbfw@3p3zu522yykv>
References: <zljergweqti7x67lg5ije2rzjusie37nslsnkjkkby4laqqbfw@3p3zu522yykv>
On Thu, Sep 11, 2025 at 5:46 PM Andres Freund <[email protected]> wrote:
> The problem leading to that is that we are currently synchronously waiting for
> IO on a buffer when AsyncReadBuffers() encounters a buffer already undergoing
> IO. If a block is read twice, that means we won't actually have enough IOs in
> flight to have good performance. What's worse, currently the wait is not
> attributed to IO wait (since we're waiting in WaitIO, rather than waiting for
> IO).
This patch no longer cleanly applies. Can you post a new version?
Thanks
--
Peter Geoghegan
view thread (28+ 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: Don't synchronously wait for already-in-progress IO in read stream
In-Reply-To: <CAH2-Wz=3_pmjM4=GLG+D2T=4uGm9dSMWbDTNzhHY3=kLoPPhaw@mail.gmail.com>
* 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