| From: | Hannu Krosing <hannuk(at)google(dot)com> |
|---|---|
| To: | "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Ants Aasma <ants(at)cybertec(dot)at>, gregsmithpgsql(at)gmail(dot)com, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: What is a typical precision of gettimeofday()? |
| Date: | 2024-06-18 15:08:57 |
| Message-ID: | CAMT0RQQ=2u5GATAMWqnfsW7baTZT_6QgRVrZXd8oFS8bk1kVbQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I plan to send patch to pg_test_timing in a day or two
the underlying time precision on modern linux seems to be
2 ns for some Intel CPUs
10 ns for Zen4
40 ns for ARM (Ampere)
---
Hannu
|
On Tue, Jun 18, 2024 at 7:48 AM Andrey M. Borodin <x4mmm(at)yandex-team(dot)ru>
wrote:
>
>
> > On 19 Mar 2024, at 13:28, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
> >
> > I feel that we don't actually have any information about this
> portability concern. Does anyone know what precision we can expect from
> gettimeofday()? Can we expect the full microsecond precision usually?
>
> At PGConf.dev Hannu Krossing draw attention to pg_test_timing module. I’ve
> tried this module(slightly modified to measure nanoseconds) on some
> systems, and everywhere I found ~100ns resolution (95% of ticks fall into
> 64ns and 128ns buckets).
>
> I’ll add cc Hannu, and also pg_test_timing module authors Ants ang Greg.
> Maybe they can add some context.
>
>
> Best regards, Andrey Borodin.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Sharma | 2024-06-18 15:10:21 | Re: Truncation of mapped catalogs (whether local or shared) leads to server crash |
| Previous Message | Andres Freund | 2024-06-18 15:02:38 | Re: consider -Wmissing-variable-declarations |