Free Clock Democratizes Atomic Accuracy
schliz writes "A new, trial network of software-based clocks could give data centers and networks the accuracy of an atomic clock for free. The so-called RADclock analyses information from multiple computers across the internet by collecting the time from each machine's internal quartz clock, the time it takes for this information to be transmitted across the network, and comparing all the information collected to determine a time that is most likely to be accurate, so machines are calibrated across the network with up to microsecond accuracy — as good as that provided by a $50,000 atomic clock, researchers say."
NTP solved this ages ago by distributing atomic clock accuracy through the network.
The only problem this will solve is where it is a private network not connected to public NTP servers (or organizations that do not trust public NTP). In that case, they would most likely be able to afford a atomic clock.
:. Ultimate Control Dedicated/VM Servers
They have atomic clocks on board and GPS receivers therefore give highly accurate time.
Donte Alistair Anderson Roberts - hi son!
Karma: Chameleon
...but in what situation would the time of day on a server or cluster need to be accurate down to a microsecond? Military, I would presume...but what else?
Living With a Nerd
I'm also pretty sure there are desktop clocks based on microcontrollers that implement ntp, so they display an accurate time without a computer.
Most data centers that really care about time nowadays install a commonly available GPS unit on site, which syncs clock time with all the atomic clocks in the flying GPS constellation.
Seriously, could the editor that greenlighted this have done a google search or something? It's getting embarrassing to read slashdot these days.
What is the resolution of the built-in clock on most PCs? An Atomic clock might have nanoscale resolution, but if a computer's clock only has microsecond resolution, then it stands to reason that you can only synch the computer to within 1 microsecond of accuracy, no?
If your computer runs Windows it is probably using SNTP to simply set the clock. PCs are notoriously bad timekeepers and so the skew that you're describing is quite commonplace. The beauty of a full NTP implementation like ntpd is that, while it can be made to sync your clock, it's mostly about calculating your clock's drift so that tick intervals can be adjusted in order to obviate "hard" time synchronization. This eliminates those very wrong time readings in the hours/days before SNTP re-syncs.
Let's just not pay attention to things like the difference between precision and accuracy anymore, it's too much work.
I mean, there's no way that the same physical limitations would apply to all quartz clocks, right?