Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?
John Naylor <johncnaylorls@gmail.com>
Attachments
- nocfbot-architecture-macros-v1.patch (text/x-patch) patch v1
On Tue, Feb 24, 2026 at 2:22 PM Lukas Fittl <lukas@fittl.com> wrote: > > On Mon, Feb 23, 2026 at 6:02 PM John Naylor <johncnaylorls@gmail.com> wrote: > > > > On Tue, Feb 24, 2026 at 5:28 AM Andres Freund <andres@anarazel.de> wrote: > > > On 2026-02-23 16:24:57 +0100, David Geier wrote: > > > > The code wasn't compiling properly on Windows because __x86_64__ is not > > > > defined in Visual C++. I've changed the code to use > > > > > > > > #if defined(__x86_64__) || defined(_M_X64) > > > > > > Independently of this patchset I wonder if it'd be worth introducing a > > > PG_ARCH_X64 or such, to avoid this kind of thing. > > > > +1 > > > > I've already borrowed USE_SSE2 for this meaning in commit b9278871f, > > but that's conflating two different things and I'd actually prefer the > > above, plus one that includes 32-bit as well. > > +1, would be good to have a consistent definition for this, I hadn't > realized this differs between platforms. John, do you want to take > care of adding that since you recently added USE_SSE2? In the attached I tried like this: /* * compiler-independent macros for CPU architecture */ #if defined(__x86_64__) || defined(_M_X64) #define PG_ARCH_X64 #elif defined(__i386__) || defined(_M_IX86) #define PG_ARCH_X32 #elif defined(__aarch64__) || defined(_M_ARM64) #define PG_ARCH_ARM64 #elif defined(__arm__) || defined(__arm) || defined(_M_ARM) #define PG_ARCH_ARM32 #endif and adjusted a couple places to suit. The Arm ones aren't used yet so I could leave them out for now. > > is_rdtscp_available() is an easy thing to delegate to my patch, but I > > agree it would be easier if that was abstracted a bit more so that a > > different leaf can be passed each time. The latter could also be used > > to simplify the frequency and hypervisor stuff as well. > > Yeah, that makes sense, agreed it'd be nice to centralize the CPU > architecture specific code that utilizes cpuid/etc. > > Looking at your v5/0002 over there, that should work well. As you > note, is_rdtscp_available is an easy delegation to your logic - I > think we can probably always fetch the 0x80000001 leaf to check for > RDTSCP presence in the proposed set_x86_features? I think that would work. Your pg_cpuid() looks like the abstraction we need. I think that would also allow my v5/0002 to avoid worrying about ordering dependencies. (It resets to check leaf 7, but some AVX features that we don't use need leaf 1) -- John Naylor Amazon Web Services
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
pg_test_timing: Show additional TSC clock source debug info
- 5ba34f6dc838 19 (unreleased) landed
-
instrumentation: Avoid CPUID 0x15/0x16 for Hypervisor TSC frequency
- 7fc36c5db550 19 (unreleased) landed
-
pg_test_timing: Also test RDTSC[P] timing, report time source, TSC frequency
- 16fca4825483 19 (unreleased) landed
-
Allow retrieving x86 TSC frequency/flags from CPUID
- bcb2cf41f964 19 (unreleased) landed
-
instrumentation: Standardize ticks to nanosecond conversion method
- 0022622c93d9 19 (unreleased) landed
-
instrumentation: Use Time-Stamp Counter on x86-64 to lower overhead
- 294520c44487 19 (unreleased) landed
-
Check for __cpuidex and __get_cpuid_count separately
- effaa464afd3 19 (unreleased) landed
-
pg_test_timing: Reduce per-loop overhead
- 82c0cb4e672d 19 (unreleased) landed
-
Refactor handling of x86 CPUID instructions
- be6a7494d2e3 19 (unreleased) landed
-
instrumentation: Drop INSTR_TIME_SET_CURRENT_LAZY macro
- 9d6294c09ed0 19 (unreleased) landed
-
Rename pg_crc32c_sse42_choose.c for general purpose
- b9278871f991 19 (unreleased) cited
-
Zero initialize uses of instr_time about to trigger compiler warnings
- 25b2aba0c3a5 16.0 landed
-
instr_time: Represent time as an int64 on all platforms
- 03023a2664f8 16.0 landed
-
Add 250c8ee07ed to git-blame-ignore-revs
- ff23b592ad66 16.0 cited