I recently benchmarked different SQlite implementations/driver for Node. Better-sqlite3 came out on top of this test: https://sqg.dev/blog/sqlite-driver-benchmark/
Deep dive into Turso, the “SQLite rewrite in Rust”
31–40 of 154 posts
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#32This is very shallow for a supposed deep dive. I'm not ready to entertain Turso as an alternative to something that is as battle tested as Sqlite.
Perhaps these are for deep divers who discuss Apple watch deep diving features than actual deep diving.
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#33At the current rate of progress I'm wondering how long it will take for llm agents to be able to rewrite/translate complete projects into another language. SQLite may not be the best candidate, due to the hidden test suite. But CPython or Clang or binutils or... The RIIR-benchmark: rewrite CPython in Rust, pass the complete test suite, no performance regressions, $100 budget. How far away are we there, a couple month…
What’s the point?
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#34I was surprised that the test suit not open source. Some info in https://sqlite.org/testing.html It looks like some parts are open source and other not. Does anyone know more about the backstory? (It looks like one is a custom program that generate fuzz test. Do they sell it to others SQL engines?)
it's their business model
it's free
but if you want the compliance paperwork, you pay for it
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#35I’d imagine this will go a bit like the rust rewrite of sudo etc. Despite the memory safety advantages at least towards the start it still ends up more fragile because the incumbent has years of testing and fixing behind it
I definitely wouldn't be surprised by bugs and/or compatibility issues over time. Especially in the near term. I'm mixed, but somewhat enthusiastic on Turso's efforts to create client-server options and replication.
In the past I've reached for FirebirdSQL when I needed local + external databases and wanted to limit the technology spread... In the use case, as long as transactions synched up even once a week it was enough for the disparate remote connections/systems. I'm honestly surprised it isn't used more. That said, SQLite is more universal and lighter overall.
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#36Where is the "networked mode" in Turso? Turso's readme and docs do not mention anything like this
They're implementing MVCC
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#37I’d imagine this will go a bit like the rust rewrite of sudo etc. Despite the memory safety advantages at least towards the start it still ends up more fragile because the incumbent has years of testing and fixing behind it
They're not aiming at replacing SQLite-in-C with SQLite-in-Rust, they're doing this so they can implement more additional functionality faster than with C's chainsaw-juggling-act semantics and the inability to access the proprietary SQLite test suite. See the features and roadmap at https://github.com/tursodatabase/turso
In other words, they are creating their own database and hitching on to the SQLite brand to market it. (That's fine though).
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#38The thing that worries me the most about Turso is that rather than the small, stable team running SQLite, Turso is a VC backed startup trying to capitalize on the AI boom. I can easily see how SQLite's development is sustainable, but not Turso's. They're currently trying to grow their userbase as quickly as possible with their free open source offering, but when they have investors breathing down their necks asking a…
I too am weary of VC incentives but:
1) It's MIT licensed. Including the test suite which is something lacking in SQLite:
https://github.com/tursodatabase/turso
2) They have a paid cloud option to drive income from:
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#39I recently benchmarked different SQlite implementations/driver for Node. Better-sqlite3 came out on top of this test: https://sqg.dev/blog/sqlite-driver-benchmark/
This reflects my experience. I also experienced very bad memory leaks when using libSQL for large write jobs. Haven't tried tursodatabase yet, but my impression by the confusing amount of packages in the Turso ecosystem is it's not ready for primetime yet.
Re: Deep dive into Turso, the “SQLite rewrite in Rust”
#40The thing that worries me the most about Turso is that rather than the small, stable team running SQLite, Turso is a VC backed startup trying to capitalize on the AI boom. I can easily see how SQLite's development is sustainable, but not Turso's. They're currently trying to grow their userbase as quickly as possible with their free open source offering, but when they have investors breathing down their necks asking a…
I too am weary of VC incentives but: 1) It's MIT licensed. Including the test suite which is something lacking in SQLite: https://github.com/tursodatabase/turso 2) They have a paid cloud option to drive income from: https://turso.tech/pricing
Elasticsearch was license under Apache 2.0 until they switched.
That says enough.