Hi Mats, Markos, On 9 Nov 2026, Mats Kindahl wrote: > The patch still helps CPU at large limits:
Could you also share a comparison with both WAL and relation pages already cached? That should make it easier to see whether the saved syscalls outweigh the additional copying, without the storage throughput limit dominating elapsed time. One part of my earlier comment still seems to apply to v2: for XLOG_FROM_STREAM, wanted is capped to readLen, which is at most XLOG_BLCKSZ. That path still fills the cache one page at a time, so it adds a memcpy without combining streaming reads. Could the fill size and valid-byte count instead be bounded by the available WAL from targetPagePtr to flushedUpto? Thank you! Best regards, Andrey Borodin.
