Re:Why is my NTP server costing $500 per year? Part 1 (2014)
by jlgaddis on Saturday December 24, 2016 @08:42PM
(#13252437)
Everyone's needs differ, I suppose, so some might consider that "decent". 10ms -- or even 50ms -- might be acceptable for many (most?) use cases but not for me.
From a quick look, my own (stratum 2) server in the pool currently has an offset of just under 1/20th of one millisecond.
Regardless, thanks for contributing to the pool!
Re:Why is my NTP server costing $500 per year? Part 1 (2014)
by bradfa on Saturday December 24, 2016 @10:38PM
(#13252768)
For another data point, here's my Digital Ocean droplet in Bangalore which sees from 10-60k queries per second depending on the time of day:
http://www.pool.ntp.org/user/bradfa
NTP runs fairly decently in a VM. Don't take my word for it — look at the graphs of my servers:
Here's my Google VM, notice the jitter is within +/- 5 milliseconds:
http://www.pool.ntp.org/scores/104.155.144.4
Here's my Hetzner VM (Germany). +/- 10 milliseconds, though I can't help but suspect the distance from the monitoring station (Los Angeles) may have more to do with it than being a VM:
http://www.pool.ntp.org/scores/78.46.204.247
Here's my AWS VM. Much worse than Google in that it's +/- 50 milliseconds, but still good enough to pass muster with pool.ntp.org:
http://www.pool.ntp.org/scores/52.0.56.137
Here's my Azure VM. It's in Singapore, and I re-deployed it last night, so the numbers are still coming in, but it has a pretty tight distribution:
http://www.pool.ntp.org/scores/52.187.42.158