Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? - Mailing list pgsql-hackers

From Lukas Fittl
Subject Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?
Date
Msg-id CAP53Pkzom4D8qT_CSNaJggV4avR1=FN6dFuiSRB5BZuYts7e=A@mail.gmail.com
Whole thread Raw
In response to Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?  (David Geier <geidav.pg@gmail.com>)
List pgsql-hackers
Hi David,

On Mon, Mar 23, 2026 at 1:00 AM David Geier <geidav.pg@gmail.com> wrote:
> > TSC calibration improvements:
> > - Pass TSC frequency to child processes for EXEC_BACKEND, this makes
> > TSC calibration usable on Windows, per off-list suggestion from Andres
> > - To support the EXEC_BACKEND change, refactor tsc_frequency_khz to
> > have a sentinel value of -1 indicating the TSC was not initialized, vs
> > 0 indicating it was initialized but isn't usable, and drop
> > has_usable_tsc variable
>
> Have you tested the latest patch set on Windows? Let me know if you want
> me to do that.

Not outside of CI - so if you could do testing on Windows, that'd be great!

FWIW, CI does now exercise the TSC calibration logic on Windows, which
is part why the last patch set added the handling of EXEC_BACKEND to
pass down the frequency to the client connections, because I otherwise
saw this impacting Windows CI runtimes - they're normal with the
version posted.

Thanks,
Lukas

--
Lukas Fittl



pgsql-hackers by date:

Previous
From: Lukas Fittl
Date:
Subject: Re: Stack-based tracking of per-node WAL/buffer usage
Next
From: Yugo Nagata
Date:
Subject: Track skipped tables during autovacuum and autoanalyze