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.
1 Like
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.
3 Likes
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.
1 Like
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)
1 Like
No resolution in Jellyfin 10.11.4, unfortunately. Devs have mentioned that an optimization pass is due soon, though.
1 Like