Re: aio/README.md comments - Mailing list pgsql-hackers

From Xuneng Zhou
Subject Re: aio/README.md comments
Date
Msg-id CABPTF7WmFQ6S1F6CmzhZOm3EXYVv9408s=ZfQhUeqVcFnZyfSA@mail.gmail.com
Whole thread Raw
In response to Re: aio/README.md comments  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
Hi,

On Sat, Aug 30, 2025 at 6:24 AM Jeff Davis <pgsql@j-davis.com> wrote:
>
> On Fri, 2025-08-29 at 12:32 -0400, Andres Freund wrote:
> > I don't really see an advantage of sync in those cases either.
>
> It seems a bit early to say that it's just there for debugging. But
> it's just in a README, so I won't argue the point.
>
> I attached some proposed changes based on my understanding.
>
> Regards,
>         Jeff Davis
>

+  These memory copies can become the bottleneck when the
+  underlying storage has high enough throughput, which is common for
+  solid-state drives or fast network block devices.

Would it be helpful to be more specific on the types of solid-state
drives like PCIe/NVMe SSD?
SATA SSDs' ~600 MB/s theoretical ceiling bandwidth might not be high
enough. The rate of out-of-date
could be less concerning since the advancement of hardwares has slowdowned.

Best,
Xuneng



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Improve LWLock tranche name visibility across backends
Next
From: Elliot Haisley
Date:
Subject: [PATCH] meson: Update meson to enable building postgres as a subproject