Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?

From: Andres Freund <andres(at)anarazel(dot)de>
To: John Naylor <johncnaylorls(at)gmail(dot)com>
Cc: Lukas Fittl <lukas(at)fittl(dot)com>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, Hannu Krosing <hannuk(at)google(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com>, Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, David Geier <geidav(dot)pg(at)gmail(dot)com>
Subject: Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?
Date: 2026-04-02 14:15:55
Message-ID: wm53ru2c7ornfvkcw37onaphsjfhzmqunaddmypvxy3hpps54d@qyaahxiut6w5
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2026-04-02 19:55:31 +0700, John Naylor wrote:
> The only change I made was to make the #include stanza in pg_cpu_x86.c
> match its neighbors.

Thanks for taking care of this one!

I'm wondering about splitting out some of the CPU detection stuff that's in
"v15 3/5 instrumentation: Use Time-Stamp Counter (TSC) on x86-64 for faster measurements"
into its own commit. As-is it's a pretty large commit doing lots of different things.

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2026-04-02 14:20:22 Re: Safer hash table initialization macro
Previous Message Heikki Linnakangas 2026-04-02 14:14:46 Re: Shared hash table allocations