4 ms·
One thing to note is that both Google and Amazon smear out the leap seconds https://developers.google.com/time/smear https://developers.google.com/time/smear so
by RcouF1uZ4gsC 8y ago
One thing to note is that both Google and Amazon smear out the leap seconds https://developers.google.com/time/smear https://developers.google.com/time/smear so that this is no longer a falsehood on AWS or GCP. I suspect, over time, more organizations will adopt this approach.
- dooglius 8y agoLeap smearing makes #3 no longer false, but #1 and #2 remain false
- Groxx 8y agoAlso worth noting that even tho it "solves" leap seconds, it does nothing to solve normal clock corrections. Clocks skew normally, and they need to be corrected eventually - nothing that I'm aware of skews across more than a couple seconds / within NTP limits. I.e. disconnect from a time server for a few days/weeks/months/etc. When you reconnect, it could be off by seconds/minutes/hours. Odds are pretty good that your system will just jump to the correct time immediately, rather than smearing it out for like N*3x longer than the difference is. The same is true any time you lose your internal clock, e.g. if your machine is shut down and its battery dies. If it were to skew across "all time since jan 01, 1970", it'd probably catch up well after the expected lifetime of the computer.