ACM Comm 2010 May Principles of Robust Timing over the Internet (Notes)

From University
Jump to: navigation, search
"Beyond Total Capture: A Constructive Critique of Lifelogging" CACM May 2010

Principles of Robust Timing over the Internet
by Julien Ridoux and Darryl Veitch, p.54-61

Principles of Robust Timing over the Internet

The key to synchronizing clocks over networks is taming delay variability. Synchronizing timing between disparate ecosystems, or even between objects withing the same ecosystem, to any acceptable degree, is impossible. This article explains that.

How to synchronize biological software running over a Darwin Machine which is event, not time driven?

People

Ideas

  1. Time is an event.
  2. Light Speed \(c\) is finite.
  3. No two artifacts can synchronize faster than \(c\). This is a hard limit.
  4. Time \(t\) is true time measured in seconds in a Newtonian universe, with the origin at some arbitrary time point.
  5. Clock \(C\) reads \(C(t)\) at true time \(t\).
  6. Constant Offset Clock Clock \(C_{o}(t)\) always reads faster than true time.
  7. Constant Skew Clock Clock \(C_{s}(t)\) always reads slower than true time.
  8. Drifting Clock Clock \(C_{d}(t)\) always reads slower or faster than true time as time goes on. In computers drift is related to computer temperature.
  9. Perfect Clock Theoretical clock \(C_{p}(t)\) that always reads true time.
  10. Skew or drift are never constant over any time interval.
  11. Synchronization Delay. Even \(C_{p}(t)\) can appear to drift due to communication delays, which always vary in the real world.
  12. Clock Uses
    1. Establish a strict order between events.
      1. A simple time counter can establish order with good accuracy, with no correction or update needed.
    2. Measure time durations between events
    3. Define a universally comparable and triggerable event label, the “time of day.”
  13. Allan Deviation plot, which measures oscillator stability (variability as a function of timescale).
  14. Feedback The Client clock sends time errors back to the Master clock for correction during the next update round.
  15. Feed-Forward The Master clock applies the correction before sending the time update.
  16. Difference Clock Tracks the time difference between two clocks.
  17. Synchronization over networks is actually impossible. For clocks, data, events, or anything else. See Einstein, A., and his articles on mechanical clock synchronization.
  18. Asymmetry Jitter Changes in synchronization, even leading to improvements, can confuse software because the jitter has an unknown validity from an unknown source.

References

  1. Ridoux, J., Veitch, D. RADclock Project[1].
Figure 1

Internal Links

Parent Article: Reading Notes