| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: About asynchronous I/O |
| Date: | 2026-06-23 12:02:54 |
| Message-ID: | CANzqJaAKAzYaGfPFLzt4ZZDs6sE5KGWuMmGWQ1oQYeC-wzHk_A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, Jun 23, 2026 at 7:26 AM bertrand HARTWIG <hartwig(dot)bertrand(at)gmail(dot)com>
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 <livadidrive(at)gmail(dot)com> 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!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | bertrand HARTWIG | 2026-06-23 12:19:14 | Re: About asynchronous I/O |
| Previous Message | bertrand HARTWIG | 2026-06-23 11:25:58 | Re: About asynchronous I/O |