←back to thread

SQLite concurrency and why you should care about it

(jellyfin.org)
353 points HunOL | 4 comments | 01 Nov 25 12:59 UTC | HN request time: 0s | source
Show context
mangecoeur ◴[01 Nov 25 15:14 UTC] No.45782293[source]▶
Sqlite is a great bit of technology but sometimes I read articles like this and think, maybe they should have used postgres. I you don’t specifically need the “one file portability” aspect of sqlite, or its not embedded (in which case you shouldn’t have concurrency issues), Postgres is easy to get running and solves these problems.
replies(11): >>45782439 #>>45782829 #>>45782906 #>>45782930 #>>45782932 #>>45783524 #>>45784757 #>>45784918 #>>45787275 #>>45788143 #>>45788886 #
1. petters ◴[01 Nov 25 19:53 UTC] No.45784757[source]▶
Jellyfin is mostly for a single household, right? Sqlite should be much more than sufficient for Jellyfin (if used correctly). Unfortunately, reading this article you get the impression that they are not using it optimally
replies(1): >>45786010 #
2. nick_ ◴[01 Nov 25 22:29 UTC] No.45786010[source]▶
Agreed. How can a media file sharing app possibly saturate Sqlite's write limit? I would use an app-level global lock on all writes to Sqlite.
replies(1): >>45788643 #
3. npodbielski ◴[02 Nov 25 08:03 UTC] No.45788643[source]▶
Probably during scanning libraries? They read hundreds of files and for each of them look for metadata in the internet like discogs and similar. So sure if implemented as async in c# you could run into this issue.
replies(1): >>45793427 #
4. nick_ ◴[02 Nov 25 21:03 UTC] No.45793427{3}[source]▶
Are you hinting at the lack of an `AsyncLock` in .NET?