I've been trying to upgrade from 10.10 to 10.11 for a while now, as the Android TV app keeps nagging me, and every attempt ended with impossibly long library scan times.
After some thorough investigation, it appeared that a Home Videos type collection causes unending scan (yet to be solved), but also that Jellyfin does a lot of writes to the config directory (either database or metadata or both). Mine's on spinning media part of a ZFS pool. I tried a few performance tuning options, such as testing the config dir with recordsize (similar to block size) of 4K, 8K, 64K, 128K and library scans fell from 30-40 minutes down to 8-13min with 4K-64K. The ZFS tuning wiki suggest 64K recordsize with LZ4 compression for SQLite workloads such as Jellyfin. That seems to work as well as 4K and 8K but likely is faster when reading thumbnails and such.
Note that upgrading to 12-rc3, which is supposed to speed up library scans did not improve scan times for me. Optimizing config/database write speed did. I cross-checked the culprit by experimenting with moving the config dir to NVMe and RAM. Both of those got the scan times down to 8-9 minutes compared to the optimized spinning media's 12-13.
So if you had upgraded (or about to) to 10.11 your library scans are (about to get) dog slow and your Jellyfin's config dir resides on spinning media, optimize its write performance for SQLite.
How do you communicate with the server outside of your network? You'd still need to expose those ports directly to the internet right? (excluding VPNs/reverse proxy etc)
It is still an issue that is easier on plex which is why I run both because I can't setup and troubleshoot vpns for all my family that has access. Plex is much easier on that way. Jellyfin is great but look what you need to mimic a fraction of plexs power π
Unfortunately for a Plex style easy to share library you need it to be centralized, handing over a lot of power to whoever is controlling it.
I mean, if you put restrictions on the requirement sure. At that point it kinda becomes a loaded question though.
If you remove the restriction, just use a cloudflare tunnel.
Yeah dont use a cloudflare tunnel for media streaming
They donβt care, that line in the ToS was removed years ago now.
I believe it was moved, not removed, and that it is now located in a different document, but still applies.
No it was definitely removed, they now have essentially βdonβt be an ass with the bandwidth.β