4 ms·
"1,000,000 journal entries per second on consumer-grade hardware." Of cause you could just add a few cents more per device hardware to not get a rock bottom clo
by mxfh 5y ago
"1,000,000 journal entries per second on consumer-grade hardware." Of cause you could just add a few cents more per device hardware to not get a rock bottom clock.
Or add a temperature Sensor and start modeling a drift compensation:
https://blog.dan.drown.org/rtc-comparison/ https://blog.dan.drown.org/rtc-comparison/
Or why reinvent a homebrew version of what looks like PTP IEEE 1588:
https://blog.meinbergglobal.com/2013/09/14/ieee-1588-accurate/ https://blog.meinbergglobal.com/2013/09/14/ieee-1588-accurat...
- jorangreef 5y agoThe reason is because this is not in fact a substitute for the clock sync service (whether that's PTP, or something that's becoming popular like Chrony). It's complementary, a clock fault failure detector. We're not trying to synchronize clocks, merely to detect when too many clocks in the cluster no longer agree. TigerBeetle needs to detect when the network is partitioned in a way such that the clock sync service (PTP or NTP etc.) is not functioning while the TigerBeetle cluster still has a functioning majority on the other side of the partition. No matter the clock sync service you use, you still need some way to verify that the clock sync is in fact happening, which is what this is. Hope that clarifies it for you!