Comment on State of the Fin 2026-01-06 | Jellyfin
avidamoeba@lemmy.ca 2 days agoMy god what a shit show.
It’s all normal though. Software development is hard and big changes mean more regressions. You do the changes when needed, then you work on squashing the bugs.
Library scan still going here. At least something is spinning because one CPU thread is pegged to 100%.
ragebutt@lemmy.dbzer0.com 2 days ago
Oh right! In admin console under server>general at the bottom there is a section called “performance”. Under this the first entry is “parallel library scan tasks limit”. Increasing this can significantly improve performance here. If it’s empty it is auto selecting. To that point if you’re running jellyfin in a docker and only allow it access to one core that would seriously limit performance here. Screenshot below, I currently have it set to 2 because I’ve done the “big” scan and I don’t need my cpu hammered when jellyfin does library scans
Additionally an issue I ran into later: under playback>transcoding enable hardware transcoding must be checked. Trickplay task was taking literal months because even though I had configured igpu transcoding correctly this has to be enabled separately. UX stuff like this is where jellyfin needs more polish; I’m sure there’s debate about this but why would this not default to on once transcoding is enabled? Who knows. Maybe just oversight.
Image
avidamoeba@lemmy.ca 1 day ago
This is going to be a bigger deal than I thought. Can’t cross 91% lib scan even if I delete the music lib and then upgrade. Even turning on debug logging doesn’t reveal anything helpful. Rolling back to 10.10 for now. Will attempt again when they force me to upgrade.
avidamoeba@lemmy.ca 2 days ago
Good note.
I seem to be suffering from this issue.