On Wed, 4 Feb 2026 at 16:23, Andres Freund <[email protected]> wrote: > I forgot another important one we really should use the fast timing for: > track_io_timing/track_wal_io_timing. The overhead of IO timing can be > noticeable on busy systems and it's hard to believe that the inaccuracy > matters. This is probably particularly relevant when measuring IO intensive > workloads where the data resides in the kernel page cache, but doesn't fit > into s_b.
I have been wanting for those two to be turned on by default with a "fast enough" clock source. But determining this seemed complicated. I think if the clock source for them is rdtsc we know that it is definitely fast enough to be on by default. -- Ants Aasma
