Re: Automatically sizing the IO worker pool

Thomas Munro <thomas.munro@gmail.com>

From: Thomas Munro <thomas.munro@gmail.com>

To: Dmitry Dolgov <9erthalion6@gmail.com>

Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2025-07-12T05:08:29Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

aio: Adjust I/O worker pool automatically.
- d1c01b79d4ae 19 (unreleased) landed
aio: Simplify pgaio_worker_submit().
- fc44f106657a 19 (unreleased) landed
aio: Remove obsolete IO worker ID references.
- b4c19da93a08 18.0 landed
- 177c1f059338 19 (unreleased) landed
aio: Regularize IO worker internal naming.
- b2afb0676337 18.0 landed
- 01d618bcd782 19 (unreleased) landed

Attachments

v2-0001-aio-Try-repeatedly-to-give-batched-IOs-to-workers.patch (text/x-patch) patch v2-0001
v2-0002-aio-Adjust-IO-worker-pool-size-automatically.patch (text/x-patch) patch v2-0002

On Wed, May 28, 2025 at 5:55 AM Dmitry Dolgov <9erthalion6@gmail.com> wrote:
> I probably had to start with a statement that I find the current approach reasonable, and I'm only curious if there is more to get out of it. I haven't benchmarked the patch yet (plan getting to it when I'll get back), and can imagine practical considerations significantly impacting any potential solution.

Here's a rebase.