public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jose Luis Tallon <[email protected]>
To: Thomas Munro <[email protected]>
To: PostgreSQL Hackers <[email protected]>
Subject: Re: Automatically sizing the IO worker pool
Date: Sun, 13 Apr 2025 19:45:40 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+hUKG+m4xV0LMoH2c=oRAdEXuCnh+tGBTWa7uFeFMGgTLAw+Q@mail.gmail.com>
References: <CA+hUKG+m4xV0LMoH2c=oRAdEXuCnh+tGBTWa7uFeFMGgTLAw+Q@mail.gmail.com>
On 12/4/25 18:59, Thomas Munro wrote:
> It's hard to know how to set io_workers=3.
Hmmm.... enable the below behaviour if "io_workers=auto" (default) ?
Sometimes being able to set this kind of parameters manually helps
tremendously with specific workloads... :S
> [snip]
> Here's a patch to replace that GUC with:
>
> io_min_workers=1
> io_max_workers=8
> io_worker_idle_timeout=60s
> io_worker_launch_interval=500ms
Great as defaults / backwards compat with io_workers=auto. Sounds more
user-friendly to me, at least....
> [snip]
>
> Ideas, testing, flames etc welcome.
Logic seems sound, if a bit daunting for inexperienced users --- well,
maybe just a bit more than it is now, but ISTM evolution should try and
flatten novices' learning curve, right?
Just .02€, though.
Thanks,
--
Parkinson's Law: Work expands to fill the time alloted to it.
view thread (24+ 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]
Subject: Re: Automatically sizing the IO worker pool
In-Reply-To: <[email protected]>
* 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