| ▲ | petters 6 days ago |
| 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 |
|
| ▲ | nick_ 6 days ago | parent [-] |
| 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. |
| |
| ▲ | npodbielski 5 days ago | parent [-] | | 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. | | |
| ▲ | nick_ 5 days ago | parent [-] | | Are you hinting at the lack of an `AsyncLock` in .NET? | | |
| ▲ | npodbielski 3 days ago | parent [-] | | I did not really inspect their code in this detail. I just did it once few years ago when I was exploring integrating with my oidc provider that use. At that time auth code looked not great with static class handling it it somehow.
Anyway I meant that if you scanning a lot of files and do some kind of operations for each of them, and obviously you need to save the result. Depending on how you do it. You could ram sqlite DB with thousands of connection. Which is not great way to do it but it is possible. |
|
|
|
