[LEAPSECS] Bloomberg announced its smear
brooks at edlmax.com
Fri Sep 23 14:35:35 EDT 2016
Hmmm. You wonder why they chose 2000 seconds, which gives a nice round
number of seconds for the duration: 2000/60=3.3... :-|
So, now there are at least 3 different smears in use by major providers
to "hide" the Leap Second from downstream systems that might be upset by
it. This produces indeterminate timestamps for the duration of their smears:
Two of them smear for 24 hours, 12 hours either side of the Leap Second
midnight, but their increments don't match -
Look Before You Leap – The Coming Leap Second and AWS (Updated)
Google Leap Smear 2015
Now Bloomberg is smearing for 2000 seconds (or is it 2001 seconds?).
Bloomberg will smear over 2000 seconds after the leap.
Meantime Microsoft avoids a smear altogether by diverging from the
common practice of introducing Leap Seconds on local timescales
simultaneous with UTC and instead introducing the Leap Second at (the
second before) midnight in each local zone. This results in integral
second increments and a symmetrical distribution the Leap Second
discontinuity across the local YMDhms representations.
The time on Microsoft Azure will be: Different by a second, everywhere
On 2016-09-23 10:45 AM, Steve Allen wrote:
> Bloomberg will smear over 2000 seconds after the leap.
> They are one of many cloud and financial operations who have,
> ironically, decided that the non-precision timekeeping through the 1960s
> (and of POSIX) is preferable to the precise time choice made by the CCIR.
> Steve Allen <sla at ucolick.org> WGS-84 (GPS)
> UCO/Lick Observatory--ISB 260 Natural Sciences II, Room 165 Lat +36.99855
> 1156 High Street Voice: +1 831 459 3046 Lng -122.06015
> Santa Cruz, CA 95064 http://www.ucolick.org/~sla/ Hgt +250 m
> LEAPSECS mailing list
> LEAPSECS at leapsecond.com
More information about the LEAPSECS