27
Optimizing SQLite for servers (kerkour.com)
submitted 3 months ago by 0x0@programming.dev to c/sql@programming.dev
7 comments fedilink hide all child comments

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 ;

top 7 comments
sorted by: hot top controversial new old
[-] Diplomjodler3@lemmy.world 3 points 3 months ago

Good article. Interesting perspective on the problem.

[-] nezbyte@lemmy.world 2 points 3 months ago

I tend to use DuckDB now instead of SQLite for my applications. Though it would be nice if it had better concurrency support.

[-] sjpwarren@programming.dev 3 points 3 months ago

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!

[-] earmuff@lemmy.dbzer0.com 1 points 3 months ago

And why would anyone use SQLite outside the embedded world, when you can get way more performance with ClickHouse?

[-] 0x0@programming.dev 3 points 3 months ago

Did you read the article?

There's more to SQLite than the embedded world and not everyone requires ClickHouse's performance.

[-] earmuff@lemmy.dbzer0.com 0 points 3 months ago

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.

[-] 0x0@programming.dev 1 points 3 months ago

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.

this post was submitted on 20 Jun 2024
27 points (100.0% liked)

SQL

450 readers
2 users here now

Related Fediverse communities:

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
Ategon@programming.dev
jnovinger@programming.dev