| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Should io_method=worker remain the default? |
| Date: | 2025-09-08 21:34:30 |
| Message-ID: | f1e19d97086cef964485dbb3ba3d7d8904709bb7.camel@j-davis.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2025-09-08 at 16:45 -0400, Andres Freund wrote:
> I don't think accelerating copying from the pagecache into postgres
> shared
> buffers really is a goal of AIO. It can be a nice side-effect, but
> not more.
Interesting. I thought that was part of the design.
> Afaict you've not explained in what even remotely plausible scenario
> you'd
> have where > 30GB/s of reads from the page cache. I continue to
> maintain that
> the workload presented does not exist in the real world.
For now, let's just consider it a test case that stressed a couple
subsystems and found some interesting effects. I think it will be
helpful context for potential improvements in 19. If I find other
interesting cases, I'll post them.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-09-08 21:45:43 | Re: shmem_startup_hook called twice on Windows |
| Previous Message | Sami Imseih | 2025-09-08 21:31:43 | Re: shmem_startup_hook called twice on Windows |