Live data from Hacker News

The end of a myth: Distributed transactions can scale

muratbuffalo.blogspot.com

31–40 of 95 posts

Re: The end of a myth: Distributed transactions can scale

#32
post #27

Earlier quoted context omitted.

What kind of hardware features are we missing on cloud?

The atomic clock is the key to enable distributed transactions and Google has a proprietary lock on their atomic clocks for Spanner.

You need this for global consistency, but for logical local (like a single entity) this is unnecessary.

Re: The end of a myth: Distributed transactions can scale

#34
post #27

Earlier quoted context omitted.

What kind of hardware features are we missing on cloud?

The atomic clock is the key to enable distributed transactions and Google has a proprietary lock on their atomic clocks for Spanner.

Do you know what is exactly proprietary in spanner? AFAIK most (all?) of the ideas existed before in the theoretical clock synchronization literature.

Re: The end of a myth: Distributed transactions can scale

#37

This is impressive, but won't have huge impact, IMO. Way back in 2015, MySQL Cluster (NDB Cluster engine) benchmarked 200m transactions/second on commodity hardware [1]. It was read-committed transactions, not snapshot isolation, but still impressive. NDB (or RonDB, the new DB by its author) uses a non-blocking 2-phase commit protocol (failed transaction coordinators are failed over) and is even open-source. Still, i…

How many machines was that? This is doing it across ~35.

105 machines with 28 cores each, says the presentation, and over infiniband. Looks like RonDB is quite impressive.

Re: The end of a myth: Distributed transactions can scale

#39
post #20

Earlier quoted context omitted.

You are definitely not within nanoseconds using NTP

I don’t think Chrony is NTP, if we are being pedantic, just NTP compatible. My servers have hardware timestamping on the network interface and chrony uses this.

That would be PTP then
Post reply on HN