top | item 46727055

(no title)

mattrighetti | 1 month ago

One quick thing I can think of is multiple writers [0]

[0]: https://turso.tech/blog/beyond-the-single-writer-limitation-...

discuss

order

ZeroCool2u|1 month ago

This is a huge differentiator. I built our internal meme platform with Turso. Really fun and easy to use.

zdragnar|1 month ago

How much internal traffic are you generating that single thread sqlite writes can't keep up?

ncruces|1 month ago

What's the isolation level? They only mention write-write conflicts.

The reason SQLite's BEGIN CONCURRENT does not greatly increase concurrency (unless you're very careful with your schema and queries) is as much due to page level conflict detection as it is because it enforces serializable isolation.

tonymet|1 month ago

isn't this just pushing the complexity around? Either my write thread manages the lock, or turso's does.

gpm|1 month ago

MVCC is a non-locking algorithm for concurrent writers that the big databases like postgres use (with caveats like aborting some transactions if conflicts would exist). It's not a matter of pushing locks around but allowing multiple threads to operate on the data concurrently.