4 ms·
The idea of spreading a leap second over a longer period is not unique to Google e.g. www.quadibloc.com/science/cal06.htm The idea itself is actually rather obv
by hillsarealiv3 11y ago
The idea of spreading a leap second over a longer period is not unique to Google e.g. www.quadibloc.com/science/cal06.htm
The idea itself is actually rather obvious.
- jpatokal 11y agoMost good ideas are obvious in hindsight. ;) But AFAIK, Google was the first to do this live and in production by hacking NTP, which is (apparently?) the same as what Amazon is doing.
- chronial 11y agoSAP Systems have been doing this for many, many years live and in production for DST adjustments. Not sure about leap seconds.
- RedNifre 11y agoWhat? How does it make sense to spread DST adjustments over a long time?
- Namrog84 11y agoWhat if in a dst jump. It had. Pay namrog84 $100 at 1:30am. Then 2 rolls around and it's 1am again and now I get paid a second time. Win! But if dst was smeared over a day. This would be easily prevented.
- fanf2 11y agoSee also Markus Kuhn's description of smoothed leap seconds from 2005: https://www.cl.cam.ac.uk/~mgk25/time/utc-sls/ https://www.cl.cam.ac.uk/~mgk25/time/utc-sls/
- a-priori 11y agoThe time-smearing technique reminds me of how the Erlang platform (ERTS) adjusts its internal timekeeping to changes in the system's clock. If the system's clock jumps, then Erlang makes its internal clock tick faster or slower than the system's clock by at most 1% in order to resynchronize. http://www.erlang.org/doc/apps/erts/time_correction.html http://www.erlang.org/doc/apps/erts/time_correction.html