Reading room / Coordination
Getting clocks to agree
Two computers can display the same time and still disagree by a small amount. Clock synchronization reduces that disagreement by comparing local time with reference sources over a network.
General educational information
Clocks keep moving
A computer clock is maintained locally, and its rate can differ slightly from another clock. The difference between displayed times is an offset. Because clocks can drift, synchronization is an ongoing activity rather than a single correction made when a device starts.
A hypothetical example
Imagine two computers recording when a shared document is opened. One clock runs ahead. Their timestamps might suggest an order that did not occur. Synchronization helps the comparison, although closely spaced events can still be difficult to order when timing uncertainty is significant.
A reply takes time
A time sample travels across a network. Network Time Protocol, or NTP, uses timing exchanges to help estimate the difference between clocks while accounting for travel time. A service can evaluate samples, select a reference and adjust the local clock rate or time.
Accuracy needs context
References can be arranged in a hierarchy. The result depends on the source, network conditions and implementation. A different time zone changes the displayed local time; it does not explain every clock offset. When reading timestamps, distinguish the displayed zone, the clockâs synchronization state and the precision of the recorded value. Extra decimal places alone do not establish that a timestamp is accurate.
Further reading: Microsoft: how the Windows Time service works.