A simple blog made with Zola and Duckquill Zola 2026-07-07T00:00:00+00:00 https://vsyrakis.dev/tags/sre/atom.xml 2026-07-07T00:00:00+00:00 2026-07-07T00:00:00+00:00 Vasilios Syrakis https://vsyrakis.dev/blog/draft-precision-time-protocol/ <p>In trading, knowing exactly <em>when</em> an event occurred is just as critical as knowing <em>what</em> occurred. Whether you’re correlating market data to tune a strategy, or proving to regulators (under frameworks like MiFID II) that your trades executed fairly, your timestamps need to be flawless.</p> <p>For most of the tech industry, time synchronization is handled by <strong>[BLANK 1: The standard internet protocol for clock synchronization]</strong>, which is accurate to a few milliseconds. In HFT, being off by a millisecond means you missed the trade completely. We need sub-microsecond, or even nanosecond accuracy.</p> <h2 id="enter-blank-2-the-ieee-1588-standard-for-time-synchronization"><a class="zola-anchor" href="#enter-blank-2-the-ieee-1588-standard-for-time-synchronization" aria-label="Anchor link for: enter-blank-2-the-ieee-1588-standard-for-time-synchronization"><i class="icon"></i></a> Enter [BLANK 2: The IEEE 1588 Standard for time synchronization]</h2> <p>To achieve this extreme level of accuracy across a datacenter, HFT networks rely on a different protocol entirely.</p> <p>Unlike the standard protocol, which largely operates in software, this specialized protocol is heavily reliant on hardware.</p> <h2 id="the-hierarchy-of-clocks"><a class="zola-anchor" href="#the-hierarchy-of-clocks" aria-label="Anchor link for: the-hierarchy-of-clocks"><i class="icon"></i></a> The Hierarchy of Clocks</h2> <p>A specialized time network operates in a strict hierarchy: At the very top is the <strong>[BLANK 3: The primary time source, usually receiving time via GPS antenna]</strong>. This appliance dictates the time for the entire network.</p> <p>As the time signals travel through network switches, the switches themselves must account for the time it takes the packet to traverse their internal circuitry. They do this by acting as a <strong>[BLANK 4: A switch that intercepts time packets, updates the time, and forwards them]</strong> or a <strong>[BLANK 5: A switch that simply calculates its own residency time and adds it to a correction field in the packet]</strong>.</p> <h2 id="hardware-timestamping"><a class="zola-anchor" href="#hardware-timestamping" aria-label="Anchor link for: hardware-timestamping"><i class="icon"></i></a> Hardware Timestamping</h2> <p>The real magic happens at the server level. If we rely on the Linux kernel to tell us when a packet arrived, we introduce jitter (as discussed in previous posts).</p> <p>Instead, SREs configure the Network Interface Cards (NICs) to perform <strong>[BLANK 6: The act of recording the time at the exact moment the packet hits the physical layer of the NIC]</strong>.</p> <p>By stamping the packet exactly as it arrives at the physical port (the PHY or MAC layer), we eliminate the variable delays caused by PCIe bus transfers, kernel interrupts, and thread scheduling.</p> <p>Building a network capable of distributing this kind of time accuracy is a core competency for any trading firm, ensuring that when they measure latency, they are measuring the code, not the clock.</p>