4 ms·
> I wanted to see how a database management system (DBMS) stores an index in both disk and memory, and how it searches through an Index...I chose SQLite for my
by IX-103 2y ago
> I wanted to see how a database management system (DBMS) stores an index in both disk and memory, and how it searches through an Index...I chose SQLite for my experiments
SQLite is a bit of an outlier in how it handles...everything, but even more so in query processing. SQLite tends to favor simplicity over performance, which causes it to implement things differently than every other DB I've worked with. You have to understand - SQLite isn't competing with other databases. It's competing with JSON and XML files for persistent storage. This means that how it implements anything tells you practically nothing about how a real database would do something.
- cogman10 2y agoMeh, it isn't really too far off from the way other DBMS servers handle storage and indexes. The principles are pretty identical (especially when sqlite operates in WAL mode).
- ngrilly 2y agoSQLite is a real database engine. I guess what you mean is that SQLite is not competing with database servers.
- ASalazarMX 2y agoAnd even that is questionable, since many web applications offer SQLite as another DB back end, and it works just fine for a wider range of workloads than one would expect.
- ngrilly 2y agoAgreed. SQLite is becoming popular on the server-side as well. The latest version of Rails making SQLite the default is particularly interesting.
- baq 2y agothe problem with sqlite has never been performance, it's always been extreme (dead)locking when writing concurrently - how does Rails get around that assuming this is actually recommended for prod deployments?
- ngrilly 2y agohttps://fractaledmind.github.io/2024/04/15/sqlite-on-rails-the-how-and-why-of-optimal-performance/ https://fractaledmind.github.io/2024/04/15/sqlite-on-rails-t...
- graemep 2y ago> SQLite isn't competing with other databases. It's competing with JSON and XML files for persistent storage It competes with both. its clearly used for local persistent storage. SO are quite a lot of other things. It also competes with other RDBMSes where a separate server process is not a requirement. That does mean it serves very different requirements, its just that its use case are a lot wider than just replacing JSON and XML files and similar.
- threatofrain 2y ago> It also competes with other RDBMSes where a separate server process is not a requirement. If you casually list off the top DB's either by usage or by recent hotness then almost all of them will have a server, but you'll also find they're basically all not embedded DB's with exception to RocksDB.