- cross-posted to:
- sqlite@programming.dev
- cross-posted to:
- sqlite@programming.dev
TL;DR?
PRAGMA journal_mode = WAL;
PRAGMA busy_timeout = 5000;
PRAGMA synchronous = NORMAL;
PRAGMA cache_size = 1000000000;
PRAGMA foreign_keys = true;
PRAGMA temp_store = memory ;
You must log in or register to comment.
Good article. Interesting perspective on the problem.
I tend to use DuckDB now instead of SQLite for my applications. Though it would be nice if it had better concurrency support.
Thank for your comment. I had heard of DuckDB but never checked it out. “why you would i need that I use postgres”… But I just found the WASM implementation and I have been looking for something like this for years. Thank you!
And why would anyone use SQLite outside the embedded world, when you can get way more performance with ClickHouse?
Did you read the article?
There’s more to SQLite than the embedded world and not everyone requires ClickHouse’s performance.
I actually did. There is still no reason to be wasteful with ressources. Why should I need to use a 4 core machine, when I could just use a single core machine?
Only because „it works“, does not make it a valid reason to use it.
Why should I need to use a 4 core machine
Just 'cos the article writer used one doesn’t mean you have to and i doubt “multiple CPUs” is a requirement for SQLite.