Discussion Overview
The discussion revolves around calculating the maximum clock skew of three nodes in a distributed system, each with different clock rates. Participants explore various methods for determining clock skew based on the nodes' tick rates and synchronization intervals with an external time source.
Discussion Character
- Technical explanation
- Debate/contested
- Mathematical reasoning
Main Points Raised
- One participant calculates the maximum clock skew as 1/15000 seconds based on the difference in tick rates between nodes N2 and N3.
- Another participant suggests that the maximum clock skew will be 200μs every ms, arguing that the 30-second synchronization interval is relevant only if all nodes assume a tick rate of 800 counts/ms.
- There is a claim that the clock skew could be calculated as -0.37 seconds and 0.19 seconds over 30 seconds based on the tick rates of N1, N2, and N3.
- One participant challenges the 200μs claim, suggesting it should be 200ms instead, and proposes an alternative calculation leading to a maximum skew of 0.56 seconds between N2 and N3.
- Another participant emphasizes that if N2 and N3 are aware of their tick rates, they would synchronize correctly within 200μs, leading to a maximum skew of 2.5μs.
- There is a request for clarification on how the 200μs figure was derived, with a reference to the common factor of 5 in the tick rates.
Areas of Agreement / Disagreement
Participants express differing views on the calculation of clock skew, with no consensus reached on the correct method or final value. Multiple competing approaches and interpretations of the problem are presented.
Contextual Notes
Participants' calculations depend on assumptions about the nodes' knowledge of their tick rates and the relevance of the synchronization interval. There are unresolved mathematical steps and varying interpretations of the clock skew concept.