Comment by cloutiertyler

Extraordinary claims perhaps, but correct ones nevertheless: https://spacetimedb.com/blog/benchmarking.

The article says that we don't provide strong durability guarantees. Pure ipse dixit. And IIRC he's already cleaned it up a little.

The shamelessness with which people published bogus claims about SpacetimeDB after this was really really astonishing. And so many were quick to dismiss the overall results based on some handwaving arguments. I wasn't prepared for it.

We should have held off on publishing until we had a deep technical blog on the subject.

If you haven't read https://spacetimedb.com/blog/benchmarking you should give it a read.

It seems like an odd choice perhaps, but I had the numbers to prove that it was simply measurably worse overall performance for most OLTP workloads.

IIRC, we don't let pure reads read the committed state while a transaction is underway. We can certainly do that in the future, but we're so far out ahead of typical database performance for most OLTP workloads we haven't even bothered.