• Sources: release, HN discussion
  • Summary: SQLite allows one write transaction at a time and a blocked writer sleeps for increasing intervals before retrying, so the lock can sit idle while writers are still asleep. Turso's MVCC engine with BEGIN CONCURRENT lets transactions start independently and commit in groups, the optimization added in this release, and at 1,000 transactions per second Turso's 99.9th percentile latency stays under 6 ms from 8 to 32 connections and falls to 2.4 ms at 32, while SQLite's rises from 730 ms at 8 connections to 1.2 s at 32. The release also completes window function support, adds WITH RECURSIVE, and makes full-text search work with MVCC.
  • Why it matters: SQLite is still faster with a single connection, and the benchmarks are open source and measured at a stated commit against SQLite 3.50.2, so the numbers can be rerun rather than taken on the vendor's word.

send feedback on this story