| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Automatically sizing the IO worker pool |
| Date: | 2025-07-12 05:08:29 |
| Message-ID: | CA+hUKGJLe-0E-wZ-is78CEHhjbC=ihMVCQLoN1dmD-j05s9qRg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 28, 2025 at 5:55 AM Dmitry Dolgov <9erthalion6(at)gmail(dot)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.
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-aio-Try-repeatedly-to-give-batched-IOs-to-workers.patch | text/x-patch | 1.9 KB |
| v2-0002-aio-Adjust-IO-worker-pool-size-automatically.patch | text/x-patch | 33.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Atsushi Torikoshi | 2025-07-12 06:53:14 | Re: Improve tab completion for COPY |
| Previous Message | Thomas Munro | 2025-07-12 04:39:43 | Re: I/O worker and ConfigReload |