New Jellyfin Server/Web release: 10.11.4

[tomstephens89]

Unfortunately performance problems causing DB locking, no login, slow WEB ui etc are still present in 10.11.4.

I have DB locking policy set to Optimistic and Parallel tasks set to 1 already.

These issues are all over GitHub, but no-one appears to be acknowledging some sort of big database handling issue?

[jellykrabbypatty]

I was hoping by now we would be mostly back to good but my server still runs extremely slow and this update didn't help at all. It actually seems slower. I really want to go back to 10.10 for now. Does anyone know best way to do this?

[Ginkoh83]

Hello team. Since the 10.11.0 update, everything has gone almost perfectly for me. Navigating through Jellyfin has even become faster than before. I’ve only encountered two minor issues.
The first one, during the 10.11.0 update, removed the movies from my collections.
The second one, which is still happening, concerns the library refresh. On previous versions, refreshing all my libraries took 1 or 2 minutes at most; now it takes about 50 minutes.
So when I want to add new media, I refresh only the specific library instead (which takes less than a minute).
I also don’t use many plugins, maybe that’s why I haven’t run into many problems (AniDB, AniList, AudioDB, MusicBrainz, OMDb, Studio Images, TheTVDB, TMDb).
For context, I’m running Jellyfin in an LXC on Proxmox.

Keep up the good work, and thanks for the continued support.

[Sea Monkey]

Is anyone running v10.11.4 and using Jellyfin for Kodi with no issues and all of the following library types tested?

- Movies
- TV Shows
- Music Videos
- Music
- Pictures

Do full sync from scratch and Kodi Sync Queue both perform without substantial delay over 10.10.7?

[Adam86]

Is anyone running v10.11.4 and using Jellyfin for Kodi with no issues and all of the following library types tested?

- Movies
- TV Shows
- Music Videos
- Music
- Pictures

Do full sync from scratch and Kodi Sync Queue both perform without substantial delay over 10.10.7?

I'm using Jellyfin on Kodi.  Noticed a massive difference in performance since 10.10.7.  Syncing is much more sluggish, I had to disable Music libraries as it froze every time. 

Sometimes the connection drops to Jellyfin and will only start working again after restarting Kodi/CoreELEC.

[djfmd783g]

just installed, running smooth. ubuntu 24.04, bare metal (i7-7567U NUC), with EGPU. Great work everybody.

[esjaysee]

So I'm about to install the update. Since 10.11.x dropped my main issue has been image loading. Now one work round although was tedious as fuck was to scroll through and let everything load...yeah pain in the ass, but I did notice with the new "aggressive" cache method that did improve load times noticably. Although nowhere near as "snappy" as 10.10.x, it makes me wonder if that's where the issues most of us are having live.

[JF2025]

@tomstephens89

Unfortunately performance problems causing DB locking, no login, slow WEB ui etc are still present in 10.11.4.
I have DB locking policy set to Optimistic and Parallel tasks set to 1 already.

I had the same locking issue with the release of 10.11.x. However, I changed the "LockingBehavior" value in the database.xml file to "Optimistic", and parallel tasks to empty in General>Settings (meaning it uses my system's core count). That fixed locking and performance issues for me, after clearing cache and restarting the server.

I note that you have parallel tasks set to 1. That did not work well for me. Hope this helps.

[raulo1985]

@tomstephens89

Unfortunately performance problems causing DB locking, no login, slow WEB ui etc are still present in 10.11.4.
I have DB locking policy set to Optimistic and Parallel tasks set to 1 already.

I had the same locking issue with the release of 10.11.x. However, I changed the "LockingBehavior" value in the database.xml file to "Optimistic", and parallel tasks to empty in General>Settings (meaning it uses my system's core count). That fixed locking and performance issues for me, after clearing cache and restarting the server.

I note that you have parallel tasks set to 1. That did not work well for me. Hope this helps.

Kinda weird that setting parallel tasks to 1 did not work well for you and that what fixed it was setting it to more than one (obviously your processor doesn't have just one core), since lowering its value is supposed to be one of the things that could prevent db locking. I guess there must be something related to db handling that's still buggy. Did you have db locking issues with parallel tasks set to 1 with the default NoLock too? Setting locking behavior to Optimistic may have helped, but it doesn't make much sense that you have more db locking with parallel tasks set to 1 than with more than 1. And did you try with Pessimistic? If so, did you also have db locking issues?

[JF2025]

@raulo1985 : I tried a combination of settings as you suggest. As I remember, I had an extremely slow and error prone scan with a setting of 1. The combination that worked for me was the "empty" parallel tasks input (system core count) with the Optimistic property in the xml. Yes, my processor has multiple cores. Full scans still take some time. With a large music collection, I expect that when doing the replace metadata on the full library. Update scans, normalisation scans, etc. are relatively fast on newly added files.

Exactly how the application manages database access would be an answer that the developers could explain much better than I could. I just settled on the settings that no longer gave me log errors associated with locking, while improving overall performance.

Also, it might be helpful to add that I did a fresh install of v 10.11.x I did not try migrating from the previous version as database migrations after refactoring can be problematic in any application. I just waited out the rescan, as my media files have good embedded tags.