> I saw suggestions to “use io_uring for maximum efficiency”, but the earlier benchmark clearly shows io_uring being significantly slower than worker for sequential scans.
What's unstated is: why does this happen? Is this a performance bug that can be fixed in later release, or an inherent io_uring limitation?
What's unstated is: why does this happen? Is this a performance bug that can be fixed in later release, or an inherent io_uring limitation?