Do you have music? I don’t know this for sure but I also wonder if music collections slow things down. My music collection is pretty massive (like 40% of my storage) and it’s a shitload of files to index.
Thankfully I don’t put my books in jellyfin because my ebook/manga library is also pretty massive. If the apocalypse occurs I’m set for the 2-3 days I’d have power after the end of times
After the migration it is recommended that you perform a full scan through the admin dashboard. We have observed that for some users, some elements might not work properly otherwise (e.g parental ratings). As of RC8 a scan for missing metadata may be required for music libraries to function properly. The first scan after the migration might also take quite a bit longer than usual, though subsequent scans should be as quick as before.
Interesting. I will say music is the weakest point of jellyfin db. Mine is currently good but I nuked my db for the new db style in 10.11 and created a new db, mainly bc of issues within music library. But this went back to like 10.9 and were probably from me fucking around in the db manually to try and override tags. I’ve since retagged my music as it was just the easier solution (artist ft artist got me all fucked up, I hated having 900 entries for like 1 artist who did frequent collabs)
This is the issue thread re the very long scanning after upgrading to 10.11
Edit: also one thing I learned from the db editing and again from the 10.11 migration is that the jellyfin db can get “stuck” in such a way that nothing I can find will overwrite db entries, even manually opening the db in an sql editor (which makes me think there are hard to find tables I could never track down but db stuff is not my forte so I dunno)
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%.
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.
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.
I seem to be suffering from this issue. Lotsa spam in the logs and the scan job doesn’t seem to be moving. The next attempt would be, revert, disable music lib and upgrade. Then deal with the music lib separately. But I’ll let it run another 12-24 hours.
Fucking hell. OK, I’ll upgrade again and wait longer. Mine’s ~15TB.
Do you have music? I don’t know this for sure but I also wonder if music collections slow things down. My music collection is pretty massive (like 40% of my storage) and it’s a shitload of files to index.
Thankfully I don’t put my books in jellyfin because my ebook/manga library is also pretty massive. If the apocalypse occurs I’m set for the 2-3 days I’d have power after the end of times
I do. It could be this:
From the release notes.
The last messages in the log are from music lib scanning. I’m leaving it be for now.
Interesting. I will say music is the weakest point of jellyfin db. Mine is currently good but I nuked my db for the new db style in 10.11 and created a new db, mainly bc of issues within music library. But this went back to like 10.9 and were probably from me fucking around in the db manually to try and override tags. I’ve since retagged my music as it was just the easier solution (artist ft artist got me all fucked up, I hated having 900 entries for like 1 artist who did frequent collabs)
https://github.com/jellyfin/jellyfin/issues/15070
This is the issue thread re the very long scanning after upgrading to 10.11
Edit: also one thing I learned from the db editing and again from the 10.11 migration is that the jellyfin db can get “stuck” in such a way that nothing I can find will overwrite db entries, even manually opening the db in an sql editor (which makes me think there are hard to find tables I could never track down but db stuff is not my forte so I dunno)
My 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%.
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.
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.
Good note.
I seem to be suffering from this issue. Lotsa spam in the logs and the scan job doesn’t seem to be moving. The next attempt would be, revert, disable music lib and upgrade. Then deal with the music lib separately. But I’ll let it run another 12-24 hours.