SQLite allows one writer at a time. Turso’s MVCC engine with BEGIN CONCURRENT removes that limit, and v0.8 is where the performance shows.View quoted post on X
p99.9 transaction latency at 32 connections:
SQLite: 1.2 s
Turso: 2.4 ms
@Peristocles1, walks through the architecture behind these numbers at @P99CONF today, 11:45 am PT / 8:45 pm CEST.
Pere Diaz
Verified account This account is verified. Learn more@Peristocles1
99 Following 251 Followers 660 Posts
Latest posts 5
I wrote a new blog post about MVCC in @tursodatabase . The post does not focus on one thing in the system but instead follows the life of a row. From birth up to ultimately its death turso.tech/blog/mvcc-row-….
Officially completed first day at @supabase! Couldn't be happier for the @tursodatabase team, wouldn't have guessed what would happen after 2 years of hacking databases.
Turso v0.8 is out!
Completementary @penberg's post, I deep dived into why our commit path wasn't scaling properly in v0.7 and what it took to achieve 500x lower tail latency.
Check out turso.tech/blog/turso-gro…
Completementary @penberg's post, I deep dived into why our commit path wasn't scaling properly in v0.7 and what it took to achieve 500x lower tail latency.
Check out turso.tech/blog/turso-gro…
0:05
1/ SQLite is fast. Until everyone writes at once.View quoted post on X
Turso 0.8.0 is out: the performance release. Under concurrent writes, up to 500x lower tail latency and 7x higher write throughput than SQLite. 🧵
Not long ago Limbo would crash on INSERT number 100, now we've crossed then 200k mark without a panic and huge number of correctness asserts.
There are still various problems with UPDATE and DELETE but we are getting there!
There are still various problems with UPDATE and DELETE but we are getting there!