From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 5E1EF1F5AE; Fri, 7 May 2021 00:13:32 +0000 (UTC) Date: Fri, 7 May 2021 00:13:32 +0000 From: Eric Wong To: meta@public-inbox.org Subject: lei timestamp resolution for mail synchronization Message-ID: <20210507001332.GA18490@dcvr> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline List-Id: Is millisecond resolution "good enough" for mail synchronization? Or maybe even seconds is sufficient... When syncing mail across machines/devices/reboots, using the system clock seems required (anybody syncing mail also uses NTP, right?). While Time::HiRes allows access to .tv_nsec for some APIs; Time::HiRes::stat converts it to a double-precision float (NV/Numeric Value in perlguts-speak). That's not enough for microsecond accuracy, even; and of course I don't think most kernels or HW is actually accurate down to the nanosecond level.