| From: | David Geier <geidav(dot)pg(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, Lukas Fittl <lukas(at)fittl(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>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reduce timing overhead of EXPLAIN ANALYZE using rdtsc? |
| Date: | 2023-01-20 06:43:00 |
| Message-ID: | 24aa958f-0463-03d4-ce54-20b277c954c6@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/18/23 13:52, David Geier wrote:
> On 1/16/23 21:39, Pavel Stehule wrote:
>>
>> po 16. 1. 2023 v 21:34 odesílatel Tomas Vondra
>> <tomas(dot)vondra(at)enterprisedb(dot)com> napsal:
>>
>> Hi,
>>
>> there's minor bitrot in the Mkvcbuild.pm change, making cfbot
>> unhappy.
>>
>> As for the patch, I don't have much comments. I'm wondering if
>> it'd be
>> useful to indicate which timing source was actually used for EXPLAIN
>> ANALYZE, say something like:
>>
>> Planning time: 0.197 ms
>> Execution time: 0.225 ms
>> Timing source: clock_gettime (or tsc)
>>
>> +1
>
> I like the idea of exposing the timing source in the EXPLAIN ANALYZE
> output.
> It's a good tradeoff between inspectability and effort, given that
> RDTSC should always be better to use.
> If there are no objections I go this way.
Thinking about this a little more made me realize that this will cause
different pg_regress output depending on the platform. So if we go this
route we would at least need an option for EXPLAIN ANALYZE to disable
it. Or rather have it disabled by default and allow for enabling it.
Thoughts?
--
David Geier
(ServiceNow)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2023-01-20 06:55:39 | Re: Time delayed LR (WAS Re: logical replication restrictions) |
| Previous Message | Vladimir Sitnikov | 2023-01-20 06:40:19 | Re: Experiments with Postgres and SSL |