What steps exactly? Upgrading from the correct version and doing a full scan afterwards? Yes I did those.
Yes. When I say I didn’t follow the steps I meant that after upgrading to 10.11 and seeing some of the slowness my first “troubleshooting” step was to restart the container instead of letting Jellyfin do the whole migration stuff, which apparently can take hours.
I since have rolled back to 10.10.7 and it’s working great again, so I will stick to that version for the time being until the JF devs get this mess sorted out.
When it’s doing the whole migration stuff you can’t access Jellyfin at all, the web ui just shows the logs. So, that must have been done already when you tried it. Doing the full library scan is a button you have to manually click. During that time it will be slow and you should just wait till it’s finished.
Today’s 8.3.2 update includes a set of improvements for Jellyfin 10.11.
We’ll be continuing to monitor the resolution of the underlying server database issues and look at making additional changes in the future, if needed.
I can confirm that with Infuse 8.3.2 (Jellyfin Server 10.11.3) loading times have improved significantly. A TV show with many items (11 seasons with 24 episodes each) that previously took 8–10 seconds to load now loads in just over 1 second. Smaller shows load almost instantly.
Many thanks to the FireCore team.
Performance worsened for me with Infuse 8.3.2. My Jellyfin instance has two libraries, Movies and TV Shows. Movies curiously loaded with excellent performance which seemed equal to that under Jellyfin 10.10.7. The TV Show library is even slower to index than with Infuse 8.3.1. Have attached a video demonstrating this. Server is running Jellyfin 10.11.3.
The database issues with Jellyfin are still present, and this may be leading to slower scanning in Infuse. Unfortunately, we have limited options for addressing these issues from the Infuse side.
However, you should see faster loading times in 8.3.2 when browsing the Jellyfin share directly and opening a series/season page.
That said, as long as you have the latest 1.5.2 version of InfuseSync installed on the server the library scanning process only needs to happen once which should mitigate how much of an impact this has on day-to-day usage.
For those maybe not familar with Jellyfin, and wonder why this may not be an issue with other clients, seems to be all about Quality, File quality.
Jellyfin does not confirm exact details of files (Unless heavy media processing is enabled) to store details like HDR 1080P it relies soley of filenames, until someone clicks play.
The reason Infuse is so slow, particularly with TV shows, and those of longer seasons is because it’s making jellyfin interact with every single episode, 1 by 1 to index it’s quality 720, 1080P etc. it doesn’t rely off the filename like jellyfin, and a lot of the other jelly based apps.
@james I request that you allow the “Auto select quality” to be turned off, until a suitable update on jelly or infuse handles this problem, making the infuse client play whatever is handed to it, rather than trying to process (The reason the client is taking 10-60 seconds)
No resolution in Jellyfin 10.11.4, unfortunately. Devs have mentioned that an optimization pass is due soon, though.
Has anyone tested with 10.11.5 to see if there are any differences in this area? I’m still holding out on upgrading 
Issue not resolved in 10.11.5, disappointingly.
When making file changes on my server, or adding new content to my jellyfin library Infuse will not detect the changes for a very long time. Am I missing some sort of setting? I have tried scanning manually with no luck
What’s the latest on this? Jellyfin will force the update to 10.11 soon for Android TV app users, so I might need to take the plunge and upgrade from 10.10.7.
All the defects @james referenced above are still open with the Jellyfin team. That said, last week I took the plunge and went to 10.11.
In my case, I first migrated my 10.10.7 instance from Windows to Ubuntu. It took multiple attempts and about 8 hours of SQL scripting to get all the paths fixed in the DB, but I got it working. After that I did all that, I upgraded it to 10.11.5.
After the upgrade, in my particular case, the biggest issue I saw was with Collections. Infuse would randomly fail Indexing when Collections were enabled. I only used this with Movies so in the meantime, in Jellyfin, I’ve:
- Deleted the Collections library
- Disabled “Automatically add to collection” for the Movie library
- Disabled the TMDb Box Sets plugin
- Removed the trigger for the Scan library for new box sets Scheduled Task
Since then, I’ve had no issues with Infuse and Jellyfin. Side note, I’m not sure exactly which defect or defects is causing the issue @nomadic originally referenced, but someone made a plugin GitHub - pelluch/jellyfin-plugin-disable-user-data: A plugin to selectively disable user data from some parts of Jellyfin to mitigate at least one of the defects ( [10.11.0] /items/counts (and probably any other api with the userId flag) is slow · Issue #15014 · jellyfin/jellyfin · GitHub ).
Issue persists in Jellyfin 10.11.6 - seems slower than 10.11.5 but I haven’t confirmed that with testing.
Thanks for the heads-up. If it’s actually slower, I’ll stick with Jellyfin 10.11.5 for now.
I am having the same issue.jellyfin 10.11.6 infuse8.3.6
Infuse can barely connect to Jellyfin.
In the meantime, server version 10.11.8 is available. Has anyone had any experience with this topic?
No change, but the project’s goals for 10.11.7 and (to a lesser extent) 10.11.8 seem to be security fixes rather than performance improvements. There is a tracker for the performance fixes, so I anticipate that they will eventually find their way into a release. For now, we either need to wait, or start submitting pull requests.