Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?

From: Andres Freund <andres(at)anarazel(dot)de>
To: David Geier <geidav(dot)pg(at)gmail(dot)com>
Cc: Lukas Fittl <lukas(at)fittl(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(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>
Subject: Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?
Date: 2025-10-22 13:32:03
Message-ID: p3ygm5nnefekhj6sfoanzwqygcz3edag7shblkidq47l3ys3r2@v2twclclhlwm
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2025-09-01 12:36:24 +0200, David Geier wrote:
> > Open questions I have:
> > - Could we rely on checking whether the TSC timesource is invariant (via
> > CPUID), instead of relying on Linux choosing it as a clocksource?
>
> Why do you want to do that? Are you concerned that Linux might pick a
> different clock source even though invariant TSC is available?

Not sure about Lukas, but I'm slightly concerned about making this a linux
specific mechanism unnecessarily.

> We could code our own check but looking at the Linux kernel code, this
> is a bit more involved if we want to do it completely right. They check
> e.g. if the TSC is also synchronized across different CPUs, which is not
> the case if they're on different chassis (see unsynchronized_tsc() ->
> apic_is_clustered_box()).

I think Linux has higher fidelity requirements than our instrumentation usage
- with linux an inaccurate clock would lead to broken timers, wrong wall clock
etc, whereas for us it's just a skewed instrumentation result.

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2025-10-22 13:55:53 Re: Eliminating SPI / SQL from some RI triggers - take 3
Previous Message Fujii Masao 2025-10-22 13:31:22 Re: Invalid primary_slot_name triggers warnings in all processes on reload