Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc?
David Geier <geidav.pg@gmail.com>
From: David Geier <geidav.pg@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Pavel Stehule <pavel.stehule@gmail.com>,
Tomas Vondra <tomas.vondra@enterprisedb.com>, vignesh C
<vignesh21@gmail.com>, Lukas Fittl <lukas@fittl.com>,
Michael Paquier <michael@paquier.xyz>, Ibrar Ahmed <ibrar.ahmad@gmail.com>,
Maciek Sakrejda <m.sakrejda@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-02-14T12:48:56Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
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
-
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
Hi! On 2/14/23 12:11, David Geier wrote: > Hi, > > I think I fixed the compilation errors. It was due to a few variables > being declared under > > #if defined(__x86_64__) && defined(__linux__) > > while being used also under non x86 Linux. > > I also removed again the code to obtain the TSC frequency under > hypervisors because the TSC is usually emulated and therefore no > faster than clock_gettime() anyways. So we now simply fallback to > clock_gettime() on hypervisors when we cannot obtain the frequency via > leaf 0x16. > > Beyond that I reviewed the first two patches a while ago in [1]. I > hope we can progress with them to further reduce the size of this > patch set. > > [1] > https://www.postgresql.org/message-id/3ac157f7-085d-e071-45fc-b87cd306360c%40gmail.com > > It still fails. I'll get Cirrus-CI working on my own Github fork so I can make sure it really compiles on all platforms before I submit a new version. -- David Geier (ServiceNow)