3 ms·
Pity they still haven't finished adding support for proper database backends. SQLite is the source of all my problems with Jellyfin as it buckles under the weig
by MrDrMcCoy 1mo ago
Pity they still haven't finished adding support for proper database backends. SQLite is the source of all my problems with Jellyfin as it buckles under the weight of my library, behaves badly on CoW filesystems, and prevents scaling my instance to multiple nodes.
- globular-toast 1mo agoI don't even have a huge library but it performs terribly on my system due to SQLite. Would love a Postgres backend.
- andai 1mo agoHuh, I always thought one of the main advantages of SQLite was supposed to be the performance. (e.g. it's one of the things they brag about on the website.)
- globular-toast 1mo agoIt's something to do with NFS. I haven't fully figured it out, but it keeps locking up for some reason. They basically say NFS is not supported.
- Avamander 1mo agoIt's performant under specific workloads. Performance degrades a lot with safe multi-client usage.
- clayhacks 1mo agoPart of this upgrade was improving the database, with the end goal of supporting other database engines like Postgres and MySQL. Unclear exact timeline of proper support but it’s on the way https://features.jellyfin.org/posts/315/mysql-server-back-end https://features.jellyfin.org/posts/315/mysql-server-back-en...
- port11 1mo agoI can’t imagine what size library causes trouble, but plugins might also be the problem with slowness or scaling. Could you manually add some indexes on misbehaving queries? I agree that SQLite might not be the better choice given many Jellyfin users are probably on ZFS or BTRFS.