ian2607
October 31, 2025, 6:50am
23
Same here, on direct mode for myself, not tried library mode.
james
October 31, 2025, 2:13pm
24
We’ve been reviewing a few reports that have come in, and it looks like the issue is on Jellyfin’s side. When opening a series, we request a list of seasons, but for many shows, the server now responds significantly slower than in previous versions. This also affects fetching time in Library mode.
Presumably a fix should come from Jellyfin, but we’re going to keep digging into potential options here.
jd9k1
October 31, 2025, 2:24pm
25
Thanks. What’s every other unaffected client doing?
mavace
October 31, 2025, 2:46pm
26
Appreciate the efforts here James! The new database implementation on Jellyfin’s side definitely needs some fine tuning from them. One thing I would be curious on though is how other projects are loading and not having issues and maybe taking a peak at their implementation. The one that comes to mind for me is Streamyfin ( GitHub - streamyfin/streamyfin: A modern Jellyfin client built with Expo ).
james
October 31, 2025, 2:49pm
27
Depending on how clients interact with Jellyfin they may or may not be affected so we may need to adjust how Infuse interacts with Jellyfin if a database fix on their side isn’t forthcoming.
jd9k1
October 31, 2025, 2:58pm
28
Even just knowing what other clients do, and communicating it to Jellyfin’s people, can help them with their fix if they feel inclined to do something about this.
same here, also when playing a video the jellyfin log spams every second this
[2025-10-31 17:22:25.496 +00:00] [ERR] [54] Emby.Server.Implementations.Session.SessionManager: Error reporting playback progress
System.MissingMethodException: Method not found: ‘System.Collections.Generic.List`1<Jellyfin.Data.Entities.User> MediaBrowser.Controller.Library.PlaybackProgressEventArgs.get_Users()’.
at Jellyfin.Plugin.PlaybackReporting.EventMonitorEntryPoint.SessionManager_PlaybackProgress(Object sender, PlaybackProgressEventArgs e)
at Emby.Server.Implementations.Session.SessionManager.OnPlaybackProgress(PlaybackProgressInfo info, Boolean isAutomated)
at MediaBrowser.Controller.Session.SessionInfo.OnProgressTimerCallback(Object state)
looks like Infuse tries to call some api method that doesn’t exist anymore in 10.11.1
james
November 1, 2025, 2:56pm
30
This one seems different. These logs show an error that occurs inside the server’s own code. If we were calling a non-existent API — it would appear during HTTP request parsing instead of a message like this. This is also unrelated to the InfuseSync plugin — as it doesn’t use any of the callbacks mentioned in the logs. Presumably, this issue would occur with any client — not just Infuse — including the web interface when the server receives playback progress updates.
FWIW, we’re not seeing this locally, and the “missing” method is actually still present in the Jellyfin source code. It seems something may have gone wrong with this server or the upgrade process.
Not sure if it helps, but messing around with the API calls I see Infuse performing seems to indicate that including the field “People” in pretty much all API calls drastically increases the response time. If you omit that field, the API is much quicker. E.g.:
Episode View: 4.2s → 0.14s
Next Up (Shows): 6.4s → 1.7s
It does seem like a regression from Jellyfin, but I also don’t see the native WebUI doing that call. It seems the native WebUI just does the following on the Show Item ID (not the Episode ID), which returns all the People for the show:
/Users/bcbaa15ab3f24fb5a49a8b7fb50b1e97/Items/baa94152cdaee0f36fa21d231773f660
opened 12:27AM - 02 Nov 25 UTC
bug
### Description of the bug
Inclusion of the "People" field in various API calls… causes significantly increased API response times compared to 10.10.X
This seems to be a regression from 10.10.X as this used to be much faster. This also seems to be the main reason why Infuse has been taking significantly longer to load since 10.11.X [0]
[0] https://community.firecore.com/t/poor-series-loading-times-with-jellyfin-10-11/57511/31
### Reproduction steps
```bash
# Items/Latest (People) - 0m18.546s
curl -H "X-Emby-Token: <redacted>" \
"https://<redacted>/Items/Latest?userId=<redacted>&fields=DateCreated,Etag,Genres,MediaSources,AlternateMediaSources,Overview,ParentId,Path,People,ProviderIds,SortName,RecursiveItemCount,ChildCount&parentId=f53fc09464c15245f5373088e52a7f1a&startIndex=0&limit=20"
# Items/Latest (No People) - 0m4.392s
curl -H "X-Emby-Token: <redacted>" \
"https://<redacted>/Items/Latest?userId=<redacted>&fields=DateCreated,Etag,Genres,MediaSources,AlternateMediaSources,Overview,ParentId,Path,ProviderIds,SortName,RecursiveItemCount,ChildCount&parentId=f53fc09464c15245f5373088e52a7f1a&startIndex=0&limit=20"
# Shows/Episodes (People) - 0m12.613s
curl -H "X-Emby-Token: <redaced>" \
"https://<redacted>/Shows/baa94152cdaee0f36fa21d231773f660/Episodes?userId=<redacted>&excludeLocationTypes=Virtual&fields=DateCreated,Etag,Genres,MediaSources,AlternateMediaSources,Overview,ParentId,Path,People,ProviderIds,SortName,RecursiveItemCount,ChildCount&seasonId=64b3d9a2f8a190b8fe9f4411e6709bd1"
# Shows/Episodes (No People) - 0m0.861s
curl -H "X-Emby-Token: <redaced>" \
"https://<redacted>/Shows/baa94152cdaee0f36fa21d231773f660/Episodes?userId=<redacted>&excludeLocationTypes=Virtual&fields=DateCreated,Etag,Genres,MediaSources,AlternateMediaSources,Overview,ParentId,Path,People,ProviderIds,SortName,RecursiveItemCount,ChildCount&seasonId=64b3d9a2f8a190b8fe9f4411e6709bd1"
```
### What is the current _bug_ behavior?
Slow API responses
### What is the expected _correct_ behavior?
Faster API responses
### Jellyfin Server version
10.10.0+
### Specify commit id
_No response_
### Specify unstable release number
_No response_
### Specify version number
10.11.1
### Specify the build version
10.11.1
### Environment
```markdown
- OS: NixOS
- Linux Kernel: Linux jellyfin-76dd7fc585-4pl4z 6.12.44 #1-NixOS SMP PREEMPT_DYNAMIC Thu Aug 28 14:31:16 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
- Virtualization: XCP-NG
- Clients: Infuse / Curl
- Browser: N/A
- FFmpeg Version: N/A
- Playback Method: N/A
- Hardware Acceleration: N/A
- GPU Model: N/A
- Plugins: InfuseSync
- Reverse Proxy: Traefik
- Base URL: N/A
- Networking: 40gb
- Jellyfin Data Storage: XFS iSCSI 4 x SSD "raid 10" ZFS
- Media Storage: N/A
- External Integrations: N/A
```
### Jellyfin logs
```shell
N/A
```
### FFmpeg logs
```shell
```
### Client / Browser logs
_No response_
### Relevant screenshots or videos
_No response_
### Additional information
_No response_
nomadic
November 3, 2025, 3:05am
32
Issue persists in Jellyfin 10.11.2/Infuse 8.3
thanks, it was indeed the “Playback Reporting” plugin which didn’t update unlike the others.
kb0
November 7, 2025, 3:50pm
34
@MetalSnake - Did updating to v17 ( Release Version 17 · jellyfin/jellyfin-plugin-playbackreporting · GitHub ) fix the issue? I’ve held off on upgrading to 10.11 until I saw this was resolved. Thx
Even though it solved the problem for MetalSnake, the issue described here is a different one. For example, I don’t have the Playback Reporting plugin installed at all. I think anekdotos provided a very important clue there.
It fixed the issue I described above. I thought it was related to the slow loading times but it wasn’t.
Also the latest Infuse beta apparently has a fix for the slow loading times.
kb0
November 7, 2025, 7:25pm
37
Got it; I’ll continue to wait. Thank you both
So there’s already a fix in the beta that might go live soon? You just made my day.
count me in the same boat that it just does not work in direct mode nor library mode. The server and the app can stream the data if i can get them to communicate long enough to load the main page, which is very rare i would love to be part of any sort of beta to test this
digaos
November 12, 2025, 2:04am
40
For those facing the issue, did you follow the steps outline in their blog post? Jellyfin 10.11.0 | Jellyfin
I just started experiencing it this week after updating my docker container install and I DID NOT follow the recommendations in this post, so I’m wondering if the issue is present even if you do follow the steps.
Thanks!
james
November 12, 2025, 2:03pm
41
Quick update.
We have a few change coming in 8.3.2 that will help improve things somewhat when loading series/season pages, but there are some core performance issues with Jellyfin 10.11 that appear in some cases and these will need to be addressed by Jellyfin on the server side.
There are some other reports of this and these four GitHub issues cover most of the performance issues we are seeing in case you want to follow along with their progress.
opened 10:28AM - 09 Aug 25 UTC
bug
### Description of the bug
Season folders can take a long while to load.
Especi… ally for shows with many series, it seems to be exponentially worse.
Inspecting network timings with chrome, the cause is the `Shows/<id>/Seasons` api call.
I can verify this with a curl to the api.
Interestingly if we call the api adding `enableUserData=false`, it will only take a fraction of a second to run.
The problem is several times worse on v10.11.0/master.
Some timings (for show with 36 series):
```
cpu v10.7.0 v10.11.0
Intel N6005 2s 6s
ARM A55 12s 47s
```
I put some performance logging in, and traced it as far as this bit of the code:
https://github.com/jellyfin/jellyfin/blob/601ce4c3b1033169d9ae615045b2780df844cd62/MediaBrowser.Controller/Entities/Folder.cs#L1702-L1714
But I don't yet know what it is doing under the hood.
I can see it is fetching userdata for one series at a time, but this alone does not explain why it takes so long. Each series takes 1.2s or more (on the A55, v10.11.0), while the query for the whole show without userdata takes 0.2s.
I also see that during the call, the cpu usage is maxed out (for 1 core at least). Perhaps also indicating more to the problem than per-series db calls.
### Reproduction steps
Using chrome to inspect network traffic, while browsing to a TV show, we can find the Season api call, with user and show ids.
We can create an api token in the dashboard, so that we can access the api via curl.
Then we can construct a curl command like:
```
TOKEN=****
SHOW=db391fa226a17534ea33faef2ead66c5
USER=023f23d597294a5a9d316e12ec9d851f
time curl -s -H "X-MediaBrowser-Token: $TOKEN" "http://localhost:8096/Shows/$SHOW/Seasons?userId=$USER&Fields=ItemCounts%2CPrimaryImageAspectRatio%2CCanDelete%2CMediaSourceCount"
...json output here...
real 0m56.424s
user 0m0.037s
sys 0m0.037s
```
### What is the current _bug_ behavior?
Shows/<id>/Seasons api call, with userdata can take many seconds to run.
### What is the expected _correct_ behavior?
The api call should be sub 1 second.
### Jellyfin Server version
Master
### Specify commit id
b00e381109d1d3b1d83da0ed678b8b27d70341d1
### Specify unstable release number
_No response_
### Specify version number
_No response_
### Specify the build version
10.11.0
### Environment
```markdown
- OS: Ubuntu 22.04
- Linux Kernel: 5.15.118
- Virtualization: no
- Clients: Browser/Curl
- Browser: Chrome
- FFmpeg Version: 4.4.2
- Playback Method: n/a
- Hardware Acceleration: none
- GPU Model: n/a
- Plugins: none
- Reverse Proxy: no
- Base URL: none
- Networking: host
- Jellyfin Data Storage: local sata SSD
- Media Storage: local sata HDD
- External Integrations: none
```
### Jellyfin logs
```shell
The Seasons api call is not logged in the code.
```
### FFmpeg logs
```shell
```
### Client / Browser logs
_No response_
### Relevant screenshots or videos
_No response_
### Additional information
I see another ticket re performance issues on v10.11.0 https://github.com/jellyfin/jellyfin/issues/14278
It does not mention this specific problem, but perhaps related to worsening performance on this version.
opened 02:34PM - 15 Oct 25 UTC
bug
### Description of the bug
All the RC builds for the latest version have given … me this issue.
### Reproduction steps
Open a TV show with a fair few seasons and episodes (in my case, it's a daily TV show I did post-production on for quite a few years and similar results with other equally large documentary series I've worked on).
### What is the current _bug_ behavior?
Seasons for a lot of things take an abnormally long amount of time to appear, yet `Cast & Crew` and `More Like This` appear long before the seasons do, if they do whatsoever. Sometimes it appears to time out as only `Next Up` appears, resulting in the seasons not appearing. Sometimes they appear after a while if I refresh, other times, they don't. The larger the number of seasons/episodes, the more frequent this problem appears to be.
### What is the expected _correct_ behavior?
That they would appear as fast as browsing through the libraries in general. Bizarre to me why this would be so slow.
### Jellyfin Server version
10.10.0+
### Specify commit id
_No response_
### Specify unstable release number
_No response_
### Specify version number
_No response_
### Specify the build version
10.11.0-rc9
### Environment
```markdown
- OS: Unraid 7.1
```
### Jellyfin logs
```shell
Nothing of note.
```
### FFmpeg logs
```shell
```
### Client / Browser logs
_No response_
### Relevant screenshots or videos
_No response_
### Additional information
_No response_
opened 01:05PM - 17 Oct 25 UTC
bug
### Description of the bug
jellyfin 10.11.0-RC9 has an issue with /Items/Counts… api (as well as for example the /Show/{showId}/Seasons api and probably every other related api.
The specific issue seems to be related to the "userId" query param in the api. any time it's added, the response time multiplies by a lot.
example data:
jf 10.10.7 /Items/Counts without userId: 301ms
jf 10.10.8 /Items/Counts with userId: 441ms
jf 10.11.0-rc9 /Items/Counts without userId:335 ms
jf 10.11.0-rc9 /Items/Counts with userId: 166 Seconds
### Reproduction steps
1a. make a call to an api that uses the userId flag (/Items/Counts in this case)
1b. open dashboard and look at the count of movies, shows, etc
2. wait for a 160+ seconds for it to answer
### What is the current _bug_ behavior?
the answer takes 160+ seconds to come
### What is the expected _correct_ behavior?
the answer should come within the first second
### Jellyfin Server version
Unstable
### Specify commit id
_No response_
### Specify unstable release number
_No response_
### Specify version number
_No response_
### Specify the build version
10.11.0-rc9
### Environment
```markdown
- OS:unraid
- Linux Kernel:6.12.24-Unraid
- Virtualization: Docker
- Clients:browser, android, bruno
- Browser: floorp, brave
- FFmpeg Version: unknown
- Playback Method: N/A
- Hardware Acceleration: vaapi
- GPU Model: AMD something (N/A)
- Plugins: AudioDB, MusicBrainz, OMDb, Studio Images, Tmdb
- Reverse Proxy: N/A
- Base URL: empty
- Networking: default? idk
- Jellyfin Data Storage: SSD
- Media Storage: 7200 rpm harddrives
- External Integrations: N/A
```
### Jellyfin logs
```shell
no relevant logs show up
```
### FFmpeg logs
```shell
N/A
```
### Client / Browser logs
nothing seemingly related shows
### Relevant screenshots or videos
_No response_
### Additional information
this is likely related to https://github.com/jellyfin/jellyfin/issues/15008 seeing as it has the same symptoms with the "same input"
opened 03:15PM - 02 Nov 25 UTC
bug
### Description of the bug
After upgrading from 10.10.7 to 10.11.1, I instantly… experienced a slow and sluggish UI. This is when browsing my library, which consists of movies and music.
To narrow it down, I tested with Postman just a single API endpoint `MusicGenres`:
`https://myJellyfin/MusicGenres`
On 10.11.1 the call takes nearly 7 seconds:
<img width="1732" height="874" alt="Image" src="https://github.com/user-attachments/assets/4103b6e9-bd65-4d79-8cd0-0fc81b2d0519" />
The same call takes on 10.10.7 roughly 500 ms:
<img width="1692" height="856" alt="Image" src="https://github.com/user-attachments/assets/5b325985-bd94-42bc-8f0f-03ea07b65b90" />
My music library contains roughly 4000 albums.
### Reproduction steps
1. Open Postman
2. Send a HTTP GET query to `https://<myDomain>/MusicGenres`
3. Check the response time
### What is the current _bug_ behavior?
UI and API response time slow.
### What is the expected _correct_ behavior?
Similar UI and API responsiveness as in 10.10.x
### Specify the build version
10.11.1
### Environment
```markdown
- OS: Docker on Ubuntu Server
- Linux Kernel: Linux minion 6.8.0-63-generic #66-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 13 20:25:30 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
- Virtualization: yes, VMWare Linux guest on Windows 11 Host
```
### Jellyfin logs
```shell
There is no log output when sending the API call above.
```
### Additional information
I know there are reports about performance problems on 10.11.1 but I think this one using the MusicGenre-API is really easy to reproduce and easy to compare with 10.10.x