Scott Laird<p>Okay, it's time for the big <a href="https://hachyderm.io/tags/ntp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ntp</span></a> and <a href="https://hachyderm.io/tags/ptp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ptp</span></a> wrap-up post. My week-long timing project spiraled out of control and turned into a two month monster, complete with 7 (ish?) GPS timing devices, 14 different test NICs, and a dozen different test systems.</p><p>What'd I learn along the way? See <a href="https://scottstuff.net/posts/2025/06/10/timing-conclusions/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">scottstuff.net/posts/2025/06/1</span><span class="invisible">0/timing-conclusions/</span></a> for the full list (and links to measurements and experimental results), but the top few are:</p><p>1. It's *absolutely* possible to get single-digit nanosecond time syncing with NTP between a pair of Linux systems with Chrony in a carefully-constructed test environment. Outside of a lab, 100-500 ns is probably more reasonable with NTP on a real network, and even that requires carefully selected NICs. But single-digit nanoseconds *are* possible. NTP isn't just for millisecond-scale time syncing.<br>2. Generally, PTP on the same hardware shows similar performance to NTP in a lab setting, with a bit less jitter. I'd expect it to scale *much* better in a real network, though. However, PTP mostly requires higher-end hardware (especially switches) and a bit more engineering work. Plus many older NICs just aren't very good at PTP (especially ConnectX-3s).<br>3. Intel's NICs, *especially* the E810 and to a lesser extent the i210 are very good at time accuracy. Unfortunately their X710 isn't as good, and the i226 is mixed. Mellanox is less accurate in my tests, with 200ns of skew, but still far better than Realtek and other consumer NICs.<br>4. GPS receivers aren't really *that* accurate. Even good receivers "wander" around 5-30 ns from second to second.<br>5. Antennas are critical. The cheap, flat window ones aren't a good choice for timing work. (Also, they're not actually supposed to be used in windows, they generally want a ground plane).<br>6. Your network probably has more paths with asymmetrical timing in it than you'd have expected. ECMP, LACP, and 2.5G/5G/10Gbase-T probably all negatively impact your ability to get extremely accurate time.<br> <br>Anyway, it's been a fun journey. I had a good <a href="https://hachyderm.io/tags/time" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>time</span></a>.</p>