A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2017-October/149950.html below:

[Python-Dev] PEP 564: Add new time functions with nanosecond resolution

[Python-Dev] PEP 564: Add new time functions with nanosecond resolution [Python-Dev] PEP 564: Add new time functions with nanosecond resolutionVictor Stinner victor.stinner at gmail.com
Tue Oct 24 11:31:48 EDT 2017
Warning: the PEP 564 doesn't make any assumption about clock
synchronizations. My intent is only to expose what the operating
system provides without losing precision. That's all :-)

2017-10-24 13:25 GMT+02:00 Antoine Pitrou <antoine at python.org>:
> NTP is layered over UDP.  The article shows base case UDP latencies of
> around 15µs over 10Gbps Ethernet.

Ah ok.

IMHO the discussion became off-topic somewhere, but I'm curious, so I
searched about the best NTP accuracy and found:

https://blog.meinbergglobal.com/2013/11/22/ntp-vs-ptp-network-timing-smackdown/

"Is the accuracy you need measured in microseconds or nanoseconds?  If
the answer is yes, you want PTP (IEEE 1588).  If the answer is in
milliseconds or seconds, then you want NTP."

"There is even ongoing standards work to use technology developed at
CERN (...) to extend PTP to picoseconds."

It seems like PTP is more accurate than NTP.

Victor
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4