4 ms·
Wow, just want to say that this parent comment is so great. Good criticisms along with demonstrated in-depth knowledge and shared for others' benefit. Did the
by Glench 3y ago
Wow, just want to say that this parent comment is so great. Good criticisms along with demonstrated in-depth knowledge and shared for others' benefit.
Did the parent comment author play with the mmap / synchronous / temp_store options in their tests? Wondering how those affect the write performance. I know those options from this article: https://blog.wesleyac.com/posts/consider-sqlite https://blog.wesleyac.com/posts/consider-sqlite
I'm running my SaaS web app with a SQLite db, Node/JS, and Litestream. Getting some number of millions of requests per month and haven't needed to dive in to tuning yet, but I'm curious about it and there's not a lot of data or guides about folks using SQLite as their production db, especially with specific languages or frameworks.
- ComputerGuru 3y agoThanks for the kind words. Those options you named will mainly change the specific performance characteristics but not have any impact on architectural matters. I.E. they’ll give you a bit more or less oomph out of a node but typically not make or break your app design. If you look at the GitHub benchmark I linked, you’ll see how the specific parameters I was referring to give order of magnitude changes in performance whereas eg something like using mmap over distinct syscalls will likely only give you single- or low double-digit gains depending on your configuration (more with speculative execution workarounds enabled on older hardware, less without or on newer). (Synchronous isn’t an pragma option that you can just enable or disable since it has actual ACID ramifications - i.e. either your usage will let you do it or it won’t.)