3 ms·
Not OP, I went back and forth about having containers etc on my NAS. I can of course have a separate server to do it (and did that) but a) it increases energy
by sersi 1y ago
Not OP, I went back and forth about having containers etc on my NAS. I can of course have a separate server to do it (and did that) but
a) it increases energy cost
b) accessing storage over smb/nfs is not as fast and can lead to performance issues.
c) in terms of workflow, I find that having all containers (I use rootless containers with podman as much as possible) running on the NAS that actually stores and manage the data to be simpler. So that means running plex/jellyfin, kometa, paperless-ngx, *arrs, immmich on the NAS and for that synology's cpu are not great.
In general, the most common requirements of prosumers with NAS is 2.5gbps and transcoding. Right now, none of Synology's offerings offer that.
But really the main reason I dislike synology is that SHR1 is vendor locked behind their proprietary btrfs modifications and so can only be accessed by a very old ubuntu...