|
|
|
|
|
by andersmurphy
20 days ago
|
|
:cache_size 1562 :page_size 4096 :journal_mode "WAL" :synchronous "NORMAL" :temp_store "MEMORY" :busy_timeout 5000 (Synchronous FULL in context where it matters) But, it depends on the shape of your data, your indexes, how much of the data you care about is filling up a page. If your distribution is more even you sometimes need more cache than a more Pareto distributed data set etc. Things like not caching prepared statements costs you more (you should almost always be caching prepared statements per connection with sqlite). You have to give things more thought at a billion sure. Partial indexes are your friend. You'll also want more cache to prevent thrashing etc. - https://andersmurphy.com/2025/12/02/100000-tps-over-a-billio... |
|