Re: AIO v2.5

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Antonin Houska <ah(at)cybertec(dot)at>, Noah Misch <noah(at)leadboat(dot)com>, pgsql-hackers(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Subject: Re: AIO v2.5
Date: 2025-07-29 16:41:01
Message-ID: aIj5nekHol8NnXKf@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

[RMT hat]

On Tue, Jul 22, 2025 at 03:51:12PM +0200, Tomas Vondra wrote:
> In general, it doesn't change the earlier conclusions at all. Most of
> the earlier observations apply to these results from these machines with
> reasonably different types of storage. So I still think we should stick
> to "worker", but consider increasing the default number of workers.
>
> It's possible there's machine with storage/hardware that would work
> better with some other io_method value, but that's why it's a GUC. The
> default should work for most systems.

Given there have been no further proposals or discussion, we have marked
the related open item as "Won't Fix". This means we plan to ship v18 with
io_method=worker and io_workers=3 by default.

--
nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Bauman 2025-07-29 17:07:19 Re: Doc update proposal for the note on log_statement in the runtime config for logging page
Previous Message Dagfinn Ilmari Mannsåker 2025-07-29 16:38:30 Re: Support getrandom() for pg_strong_random() source