Live data from Hacker News

Open-sourcing a more precise time appliance

engineering.fb.com

11–20 of 188 posts

Re: Open-sourcing a more precise time appliance

#11
post #5
post #3

Why does Facebook need a precision time server?

From the article: "More accurate time keeping enables more advanced infrastructure management across our data centers, as well as faster performance of distributed databases."

That seems rather ambiguous and doesn't really explain why having more time precision results in faster performance or 'advanced infrastructure management'.

I can understand why a stock broker or trading firm requires PTP to enable precise date-stamps for auditing/validating trades.

I don't see how having a time granularity on the order of picoseconds is needed for a data center.

Re: Open-sourcing a more precise time appliance

#13

Off topic: I'm reminded of a very small unit of time that was devised to be a least common multiple of various division of time like 24fps, 30fps, 44.1kHz, and a ton of others in video and audio. Does anyone remember what this unit was?

I think you might be referring to this https://en.wikipedia.org/wiki/Flick_(time)

Re: Open-sourcing a more precise time appliance

#14

Off topic: I'm reminded of a very small unit of time that was devised to be a least common multiple of various division of time like 24fps, 30fps, 44.1kHz, and a ton of others in video and audio. Does anyone remember what this unit was?

Do you mean the facebook/oculus flicks? Wonder why the repo is archived...

https://github.com/facebookarchive/Flicks

ninjaed :(

Re: Open-sourcing a more precise time appliance

#15
post #11
post #5

Earlier quoted context omitted.

From the article: "More accurate time keeping enables more advanced infrastructure management across our data centers, as well as faster performance of distributed databases."

That seems rather ambiguous and doesn't really explain why having more time precision results in faster performance or 'advanced infrastructure management'. I can understand why a stock broker or trading firm requires PTP to enable precise date-stamps for auditing/validating trades. I don't see how having a time granularity on the order of picoseconds is needed for a data center.

In distributed databases that offer transaction semantics, they need timestamps to order transactions that take place. A tighter synchronization of clocks mean they can execute transactions faster because they can reduce the amount of time they wait (based on the potential clock drift between machines in the data center)

Re: Open-sourcing a more precise time appliance

#17
post #13

Off topic: I'm reminded of a very small unit of time that was devised to be a least common multiple of various division of time like 24fps, 30fps, 44.1kHz, and a ton of others in video and audio. Does anyone remember what this unit was?

I think you might be referring to this https://en.wikipedia.org/wiki/Flick_(time)

Also, somewhat related, the "TU" https://en.m.wikipedia.org/wiki/TU_(Time_Unit)

Re: Open-sourcing a more precise time appliance

#18
A few years back I was interested in microsecond-precise timekeeping.

My experience was GPS-backed network clocks were surprisingly cheap - but PTP-aware network switches were surprisingly expensive.

And though I thought I could cut the cost of a grandmaster clock from $2000 down to $200, I figured there'd be no point if I then have to connect it to a $20,000 network switch.

I wonder how Facebook are connecting their precise new time servers to their regular servers?

Re: Open-sourcing a more precise time appliance

#19
post #4

I'm still unclear why they need the MAC on top of the GNSS reception. I can understand if it's just to provide holdover in event of GNSS signal loss, but they seem to be saying that it provides better precision when you've got both.

For anyone wondering, MAC = Miniature Atomic Clock. From the vendor product page:

> Microchip’s next-generation MAC-SA5X miniaturized rubidium atomic clock produces a stable time and frequency reference that maintains a high degree of synchronization to a reference clock, such as a GNSS-derived signal, despite static g-forces or other factors. Its combination of low monthly drift rate, short-term stability and stability during temperature changes allow the device to maintain precise frequency and timing requirements during extended periods of holdover during GNSS outages or for applications where large rack-mount clocks are not possible.

* https://www.microsemi.com/product-directory/embedded-clocks-...

Article by some folks from the manufacturer giving details on the capabilities (with graphs and such):

* https://www.gpsworld.com/new-miniature-atomic-clock-aids-pos...

Generally: if accurate positioning, navigation, and timing (PNT)—especially timing—is important in your infrastructure, then you need to plan for GNSS outages.

> In the event of the GNSS signal loss, we need to make sure the time drift (aka holdover) of the atomic-backed Time Card stays within 1 microsecond per 24 hours. Here is a graph showing the holdover of the atomic clock (SA.53s) over a 24-hour interval. As you can see, the PPS drift stays within 300 nanoseconds, which is within the atomic clock spec.

* Article.

Re: Open-sourcing a more precise time appliance

#20
post #11
post #5

Earlier quoted context omitted.

From the article: "More accurate time keeping enables more advanced infrastructure management across our data centers, as well as faster performance of distributed databases."

That seems rather ambiguous and doesn't really explain why having more time precision results in faster performance or 'advanced infrastructure management'. I can understand why a stock broker or trading firm requires PTP to enable precise date-stamps for auditing/validating trades. I don't see how having a time granularity on the order of picoseconds is needed for a data center.

See https://cloud.google.com/spanner/docs/true-time-external-con...

It should explain how clock uncertainty relates to throughput of causally-related transactions.

Post reply on HN