Re: AIO v2.5 - Mailing list pgsql-hackers

From Andres Freund
Subject Re: AIO v2.5
Date
Msg-id i6qpoaiyjfswa6n46qd2hk3g3icbfd4i6auri7owtif46zttba@ayvgewa5x3b6
Whole thread Raw
In response to Re: AIO v2.5  (Tomas Vondra <tomas@vondra.me>)
List pgsql-hackers
Hi,

On 2025-04-23 00:38:01 +0200, Tomas Vondra wrote:
> There's an open item related to this commit (247ce06b883d), based on:

Oops, forgot to reply.


>     For now the default io_method is changed to "worker". We should re-
>     evaluate that around beta1, we might want to be careful and set the
>     default to "sync" for 18.
> 
> FWIW the open item is in the "recheck mid-beta" section, but the commit
> message says "around beta1" which is not that far away (especially if we
> choose to do beta1 on May 8, with the minor releases).

I think we certainly should wait for at least beta1 (not that we have a choice
now), to make sure all of this gets at least some coverage.


> What information we need to gather to make the decision and who's
> expected to do it? I assume someone needs to do run some benchmarks, but
> is anyone working on it already? What benchmarks, what platforms?

I guess I'd say "the community". I think it should depend on how many problems
we find, be it correctness or performance regressions. I don't know how to
make that call without seeing how things are going during beta.

And yes, I think this should involve some benchmarking too - generally a good
thing to do during beta, and if it involves AIO, all the better.


> FWIW I'm asking because of the RMT, but I'm also willing to do some of
> the tests, if needed - but it'd be good to get some guidance.

More testing would be welcome!

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: disabled SSL log_like tests
Next
From: Andres Freund
Date:
Subject: Re: Support for runtime parameters in injection points, for AIO tests