[metrics-bugs] #33896 [Metrics/Consensus Health]: Depictor: stop claiming so many digits of precision for clock skew
Tor Bug Tracker & Wiki
blackhole at torproject.org
Tue Apr 14 11:34:49 UTC 2020
#33896: Depictor: stop claiming so many digits of precision for clock skew
--------------------------------------+---------------------
Reporter: arma | Owner: tom
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Metrics/Consensus Health | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
--------------------------------------+---------------------
Comment (by teor):
NTP is accurate to within 1-100 milliseconds:
https://en.m.wikipedia.org/wiki/Network_Time_Protocol
So we definitely don't need to show the third digit.
It's unlikely we will ever care about the first or second digit. But if
there are ever race conditions in the authority voting code, it could be
useful to know which authority goes first.
It's worth noting that we show consensus download times in milliseconds.
So maybe we could use millisecond precision for consistency?
https://consensus-health.torproject.org/#downloadstats
That said, most of the other times are in seconds.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33896#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the metrics-bugs
mailing list