Release 10.9.4 · jellyfin/jellyfin (github.com)

submitted 6 months ago* (last edited 6 months ago) by Mountaineer@aussie.zone to c/jellyfin@lemmy.ml

13 comments fedilink hide all child comments

https://forum.jellyfin.org/t-new-jellyfin-server-web-release-10-9-4

you are viewing a single comment's thread
view the rest of the comments

[-] st3ph3n@midwest.social 4 points 6 months ago

I assume I should probably wait for my multi-day running Trickplay task to finish before attempting an update, right? :)

[-] Mountaineer@aussie.zone 4 points 6 months ago

I've updated 10.9.1 -> 10.9.2 -> 10.9.3 (and I'm about to do .4) and I just manually fire off the trickplay generating task after each update.
It quickly walks through the files that have already been done and then resumes processing from where it left off.
Currently at 13% after like 10 days or whatever it is.

[-] ghoscht@discuss.tchncs.de 2 points 6 months ago

How long has yours been taking? Mine has been running for roughly a week and it's now on 98% That really surprised me since I don't even have that much data. It's sadly also just running on one core.

[-] st3ph3n@midwest.social 3 points 6 months ago* (last edited 6 months ago)

Mine's been running for about 5-6 days now, also not a huge library. I'm running Jellyfin in an LXC container on a host with 16 CPU cores. Started with 4 cores, but have bumped it up to 8. I have noticed that when it is generating the Trickplay images for h.264 content it only uses about 8% of the available CPU resources. When generating images for x265 it uses about 60-70%.It doesn't seem to matter what the priority for the trickplay job is set to.