-
-
Notifications
You must be signed in to change notification settings - Fork 77
Open
Description
Describe the bug
A clear and concise description of what the bug is.
Environment Details (please complete the following information):
- OS: Kubernetes v1.32.8+k3s1 on Ubuntu 24.04.
- Browser: N/A
- Jellystat Version 1.1.6
- Jellyfin Version 10.11.0
To Reproduce
Steps to reproduce the behavior:
- Install Jellyfin, import lots of media
- Install Jellystat and connect to media
- Inspect Jellyfin CPU usage after some time
Expected behavior
Jellystat should not cause that much CPU load during inital import
Screenshots
The Drop in CPU usage comes from killing the Jellyfin pod.
Task Logs
If applicable, add Task Logs for your problem.
Container Logs
Everyonce in a while jellystat shows:
[Worker Log]: [JELLYFIN-API]: Unexpected status code: 504
[Worker Log]: [JELLYFIN-API]: Unexpected status code: 504
[Worker Log]: [JELLYFIN-API]: Unexpected status code: 504
But 504s should not cause the jellyfin server to spike as much.
Additional context
I suspect that Jellystat just opens too many connections and possibly doesnt close them.
I have 1230 Movies and 9000 TV Show episodes, so its a bit of data to import.
Metadata
Metadata
Assignees
Labels
No labels