On Wed, Mar 12, 2025 at 9:02 PM Melanie Plageman <melanieplage...@gmail.com> wrote: > > Thanks for taking a look. I've pushed the patch to increase the > default effective_io_concurrency.
Cool, anything > 1 is just better. Just quick question, so now we have: #define DEFAULT_EFFECTIVE_IO_CONCURRENCY 16 #define DEFAULT_MAINTENANCE_IO_CONCURRENCY 10 Shouldn't maintenance be now also at the same value (16) instead of 10? Also, fc34b0d9de27 (5 years ago by Thomas) states about m_io_c: "Use the new setting in heapam.c instead of the hard-coded formula effective_io_concurrency + 10 introduced by commit 558a9165e08.", so there was always assumption that m_io_c > e_io_c (?) Now it's kind of inconsistent to see bitmap heap scans pushing more IOPs than recovery(!)/ANALYZE/VACUUM or am I missing something? No pressure to change, just asking what Your thoughts are. -J.
