2025-03-01, 05:07 PM
(This post was last modified: 2025-03-01, 05:08 PM by Efficient_Good_5784. Edited 1 time in total.)
(2025-03-01, 07:18 AM)scavenger1801 Wrote: Have you made any updates to your yaml file that make things run smoother since you first created this?No. The platform as a whole (Jellyfin and Synology) have been stable enough where no changes have been needed since I installed Jellyfin.
I actually migrated my Jellyfin server to another machine with better hardware.
That's the only guaranteed way you can get better/smoother performance.
I did have my DS920+ acting as a backup Jellyfin server. I would rsync my main Jellyfin config folder to the Synology NAS.
I then added a script through Synology's GUI that modified some config files to disable scheduled tasks before starting the container with the updated config folder (no use in doing the work my main Jellyfin server already did).
I finally retired the DS920+ since I built another PC to mirror my main custom server.
Being frank, Synology units do fine for data storage and access. However, they're a bit underpowered for something like Jellyfin due to the CPU choice and very low amount of pre-installed RAM.
If your Synology unit has an iGPU, it works fine. Just don't expect stellar performance with Jellyfin.
I would also recommend to avoid running lots of apps/containers at once as it will put a damper on your NAS's performance. Especially since everything runs off of the HDDs on a Synology (OS and all), which means everything is competing for the limited I/O of the HDDs.
(2025-03-01, 07:18 AM)scavenger1801 Wrote: I assume still no fix for HDR (I don't have a lot of HDR content so I don't care too much) but would love a fix if there is one.I believe something is in the works for HDR that will finally make it work properly with Synology units.
Still, the blame here is on Synology not updating their Linux kernel.
(2025-03-01, 07:18 AM)scavenger1801 Wrote: Also with this setup what is the easiest/most efficient way to update Jellyfin moving forward?
If you're using the "latest" tag for the Docker image, all you have to do is stop and rebuild the project to recreate the container with the newest image.
I personally specify a specific image tag. So I just stop the project, then edit the tag to be the newest tag, and rebuild.
Just make sure to always make a backup of the config folder in case you don't like what a new version does.