News for hackers. Stuff that matters.
Re:Clockwork raises $21M to keep server clocks in sync by paxys on Friday March 18, 2022 @10:08PM (#30730226)
None of the services you mentioned need even close to nanosecond precision between servers to operate. Applications that do (other than the ones in the article like Spanner) are concentrated in supercomputing/scientific computing and spend a LOT of money on the problem. So yeah if you are letting your clocks drift by multiple seconds you aren't "using time" in any real sense.

If these folks can achieve what they want at a couple orders of magnitude cheaper than current prices then you are absolutely going to see a lot more regular use cases show up to take advantage of it.

Re:Clockwork raises $21M to keep server clocks in sync by bitcharmer on Saturday March 19, 2022 @02:13AM (#30731577)
> None of the services you mentioned need even close to nanosecond precision between servers to operate. Applications that do (other than the ones in the article like Spanner) are concentrated in supercomputing/scientific computing and spend a LOT of money on the problem

No, not really. I work in finance (HFT, systematic market making) and this industry heavily relies on high precision clock sync. It's even regulated by law (MiFID II); in practice everyone on the street uses PTP because if you don't know how fast you're really going or where your latency spikes you already lost the race, just don't know about it.

There's a couple of other domains where micro- and nanosecond level time sync is of paramount importance. PTP has become much cheaper over the years especially when you are in a data centre and can get it as a service instead of setting up grand-masters, slaves, GPS antennas, etc.

This statement just reads like badly researched topic on their part.

Re:Clockwork raises $21M to keep server clocks in sync by lrhegeba on Saturday March 19, 2022 @01:45PM (#30735851)
especially the Huygens-implementation delivering accuracy in nanoseconds could be some part of its secret sauce (https://en.wikipedia.org/wiki/Clock_synchronization#Huygens)
Re:Clockwork raises $21M to keep server clocks in sync by pclmulqdq on Saturday March 19, 2022 @12:43AM (#30731112)
They can't do better than a microsecond or so without hardware timestsmps. There aren't a lot of applications that seem to need anything between milliseconds and nanoseconds. MiFID II did open a nice market in finance, but many of those companies use PTP anyway.

I considered starting a competitor in 2018 when I first saw this company, but I don't have the same connections to customers that these guys do.

My conclusion was that PTP precision with software timestamps would be a good company, but not something between. I hope they can prove me wrong!

Re:Clockwork raises $21M to keep server clocks in sync by dan-robertson on Saturday March 19, 2022 @07:20AM (#30732911)
My understanding is that PTP is neither necessary nor sufficient. The main advantage of it is that some hardware will only support adding hardware timestamps to PTP messages (ie you want to use the time packets left/arrived at your network card rather than the time you processed them in the kernel/userspace). But I think the specialness of PTP can lead to dealing with a lot of bugs from bad implementations.
Re:Clockwork raises $21M to keep server clocks in sync by Gelob on Friday March 18, 2022 @10:24PM (#30730319)
Telco workloads and 5g require precise time using technologies like ptp. The cheaper, more commodity those solutions get the better.
Re:Clockwork raises $21M to keep server clocks in sync by _3u10 on Saturday March 19, 2022 @12:26AM (#30731006)
If only these devices had a clock capable of measuring time to within 1 nanosecond.

If one has such an accurate clock they might be able to accurately plot their position on earth to within 1 ft merely by checking the timed pulses of orbiting satellites.

Re:Clockwork raises $21M to keep server clocks in sync by jazzyjackson on Saturday March 19, 2022 @05:17AM (#30732341)
I guess you're downvoted for being sarcastic or maybe people don't know 20 dollar GPS chips provide a ~10 nanosecond resolution clock
Re:Clockwork raises $21M to keep server clocks in sync by SAI_Peregrinus on Saturday March 19, 2022 @09:44AM (#30733641)
And GPS-disciplined oven controlled crystal oscillators (OCXOs) provide some of the best frequency accuracy and stability around. They range from about a hundred dollars up through a few thousand, depending on phase noise.
Re:Clockwork raises $21M to keep server clocks in sync by _3u10 on Saturday March 19, 2022 @02:04PM (#30736050)
Haha I have no idea. But yeah just call the GPS algo a Time AI and voila, $21 m in funding to go get some kids in shenzen to put a GPS chip on a USB, PCIe, NVME slot.

Hey look we got a GPU to learn the Kalman filter algo.

Many are actually better than 10 ns basically a 1 foot CEP is 1 ns. If they are fixed and always on the accuracy it can build over a day is incredible.

Re:Clockwork raises $21M to keep server clocks in sync by jazzyjackson on Sunday March 20, 2022 @01:37PM (#30744713)
granted it does need an unobstructed view of the sky, so getting it on a PCI-e board would be an innovation (:
Re:Clockwork raises $21M to keep server clocks in sync by krisoft on Saturday March 19, 2022 @10:07AM (#30733796)
> So yeah if you are letting your clocks drift by multiple seconds you aren't "using time" in any real sense.

If you arrive to the railway station 10 minutes +-2 minutes before your train leaves you are using time. In a very real sense. In robotics we sync multiple computers on the robot to about miliseconds, that is using time. In a real sense.

Maybe more accurate, cheaper sync will enable more applications. Maybe it is a good business to specialise on it. But saying that nobody excep for Google, CockroachDB or someone doing database things uses time is bulshit and can be called out for what it is.

Re:Clockwork raises $21M to keep server clocks in sync by ctvo on Saturday March 19, 2022 @10:59AM (#30734279)
> If you arrive to the railway station 10 minutes +-2 minutes before your train leaves you are using time. In a very real sense. In robotics we sync multiple computers on the robot to about miliseconds, that is using time. In a real sense.

Why are you in a very specific technical discussion correcting what is obvious? Yes, you're using time. You're not using time at the precision this company is targeting. At that precision, there are few current use cases, but if they make it cheaper, there will be more. What's there to argue here? You're offended you're not being included as users of time?

"We're lunching more accurate satellite imaged maps. The current users are largely nation states and niche industries due to its cost. This will enable more map use cases"

I use Google Maps all the time. I used it for my last trip! How dare you.

Re:Clockwork raises $21M to keep server clocks in sync by krisoft on Saturday March 19, 2022 @05:46PM (#30737845)
> You're offended you're not being included as users of time?

Please refrain from personal attacks. It is unecessary and doesn’t add to the conversation. Thank you.

> I use Google Maps all the time. I used it for my last trip! How dare you.

Do note that your example didn’t say “nobody uses maps”. If an imaginary salesperson would say “nobody uses maps” I would call bulshit on that too.

> Yes, you're using time.

Great, so the company representative should simply not say “nobody is using time”. And the commenter I was responding to shouldn’t say that applications which are fine with a lower accuracy “aren't ‘using time’ in any real sense”.

Heck, all I know maybe nanosecond accuracy is where the bees knee is, and everyone is going to be amazed by the awesome new applications it is going to enable. But you don’t need to disregard all the history of timekeeping and all the current applications to make that point.

On 28 April 1789 a mutiny broke out on HMS Bounty. The ship’s former captain, departing on a rowboat, demanded that the mutineers give him K2 the ship’s chronometer. The mutineers refused, because the chronometer was worth about as much as the whole ship, and they needed it for their onward navigation. Somebody should have told them that they are not using time in any real sense. Probably they would have laughed at that idea.

Re:Clockwork raises $21M to keep server clocks in sync by gnufx on Saturday March 19, 2022 @10:09AM (#30733811)
What are those applications? They've passed me by unless that's meant to cover large-scale physics measurements of some sort. I don't understand how it would even make sense in mainstream supercomputers. It should be good to synchronize OS scheduling in HPC nodes to minimize jitter in tightly-coupled applications, but that's not ns stuff and I haven't come across it actually being done (though Bull had some support as free software).

I don't see how something like Kerberos or TOTP, that fails without some sort of synchonization, can be defined as not "using time" in a real sense. (If cluster nodes were drifting by seconds, I'd be checking them, even if that was only going to affect something like make.)

Re:Clockwork raises $21M to keep server clocks in sync by ignoramous on Saturday March 19, 2022 @10:55AM (#30734238)
Google uses precision time (SunDial) for observability, telemetry, congestion control too: https://www.youtube.com/watch?v=GEXP68yNPPM
Re:Clockwork raises $21M to keep server clocks in sync by Saris on Friday March 18, 2022 @10:46PM (#30730434)
Makes me curious how accurate a GPS clock is, they must be pretty good given the timing precision needed for accurate positioning.
Re:Clockwork raises $21M to keep server clocks in sync by WinterMount223 on Friday March 18, 2022 @11:03PM (#30730545)
For GPS precision is much more important than accuracy.
Re:Clockwork raises $21M to keep server clocks in sync by Dylan16807 on Saturday March 19, 2022 @12:05AM (#30730886)
Precision vs. accuracy of what measurement?

For GPS to work at all, you need very accurate knowledge of the offset between each satellite's signal.

The only way I can think of to have precision but not accuracy is if you design a system where there's a buffer between the antenna and the signal processing and you don't know how long the buffer is. Is a design like that a practical concern?

Re:Clockwork raises $21M to keep server clocks in sync by karpierz on Saturday March 19, 2022 @12:08PM (#30734919)
They're saying that as a receiver of GPS signals, it doesn't matter if your clock is out of sync with everyone else's clocks, as long as it measures the length of a nanosecond accurately.
Re:Clockwork raises $21M to keep server clocks in sync by Dylan16807 on Saturday March 19, 2022 @02:09PM (#30736123)
But GPS gives you a clock signal.
Re:Clockwork raises $21M to keep server clocks in sync by WinterMount223 on Saturday March 19, 2022 @10:58AM (#30734271)
Of UTC. Theoretically GPS can work out of sync with respect to UTC as long as all satellites are in sync among themselves.
Re:Clockwork raises $21M to keep server clocks in sync by Dylan16807 on Saturday March 19, 2022 @02:14PM (#30736170)
Oh, you're talking about a theoretical situation where the GPS satellites are reprogrammed to use a different synchronization source? Personally I'd still call that highly accurate, but to a different time standard. But I see where you're coming from.
Re:Clockwork raises $21M to keep server clocks in sync by ahazred8ta on Saturday March 19, 2022 @12:42AM (#30731108)
With specialized GPS receivers, about +/-2ns. Closer to 40ns with commercial receivers.
Re:Clockwork raises $21M to keep server clocks in sync by nightfly on Friday March 18, 2022 @10:52PM (#30730485)
statum-1 time server