Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect and correct for clock skew #8

Open
phord opened this issue Dec 2, 2014 · 0 comments
Open

Detect and correct for clock skew #8

phord opened this issue Dec 2, 2014 · 0 comments

Comments

@phord
Copy link
Owner

phord commented Dec 2, 2014

After we run a couple of hours we should have a pretty good idea of how wrong our internal chronometer is. Calculate the wrongness and adjust our operational speed accordingly. For example, if we find that two hours have passed on our internal counters but the NTP server indicates 2 hours and 12 seconds have passed, we know we are running slow. We need to increase our speed by 0.17%, for example by adding one second every 600 seconds.

To start with, we can just calculate the skew and report it. Useful to verify steady calibration over time. Later we can add actual skew adjustment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant