Help Reviewing My Server Setup?
-
Let's be honest - in this community NAS means "my do-everything server that may have a RAID and probably also shares storage".
-
quicksync should let the i3 handle jellyfin just fine if you're not going beyond 1080p for a couple of concurrent users. Especially if you configure the Nice values to prefer jellyfin over immich.
I'm not aware of the platform for the n300 because it might be worth the initial setup, and have some room to upgrade the CPU later if it causes trouble.
If OP is going for multiple systems, I'd definitely agree on making one of them a pure NAS and let a more upgradable system run the chunky stuff.
-
The advantages you gain with running a hypervisor on something like ZFS is immeasurable, for snapshotting, replication, snapshot backups and high availability. You don't have to quiese machines to back them up and you can do instant COW snapshots before upgrades.
KVM doesn't really have overhead, that's the kernel part. Maybe a bit of RAM, but with LXCs it's negligible.
-
I think you're doing it wrong. LXCs boot almost instantaneously on a hypervisor since they hijack the host kernel, I'd be surprised if my CTs take 5 seconds.
I would agree on the live migration issue but I guess you pick your services accordingly. I have a VM that runs docker and a LXC docker host, and I pick my containers for each accordingly.
-
How on earth are you getting 5 second boot time with LXC? My containers take around 10 minutes to boot while VMs take a few seconds. Also LXC networking seems to break randomly.
-
@possiblylinux127 @ikidd Something sounds wrong there. I exclusively use LXC containers because I loathe docker and my containers boot basically instantly, and the networking is rock-solid.
-
I have no idea what you have going on, I've never seen LXCs take that long, even if I include the time it takes to down the containers and bring them up after a reboot.
What are you using for running them? I just tested my docker LXC and it took 16 seconds from when I typed "reboot" to having a login prompt. And that's on an ancient R410 server running proxmox.
-
quicksync should let the i3 handle jellyfin just fine if you’re not going beyond 1080p for a couple of concurrent users. Especially if you configure the Nice values to prefer jellyfin over immich.
Most of my content is 4K h264. You may be right on the 1080 but I don't have content at that resolution generally.
Worst case scenario he can always keep the N300 for other stuff if it doesn't work out.
-
Mount your NFS in the fstab and make sure you have docker set to wait until the mount is working. Here is a guide. https://davejansen.com/systemctl-delay-start-docker-service-until-mounts-available/
I've only had to delay on my N100s.
So I have the mounts set and then just use those paths in my compose. All my machines have the same paths.
-
I didn't think OP was going the ZFS route so it wouldn't matter on that point.
His Server 2 will be running on the red line imho so any overhead would have impact.
-
That is not my experience at all...
Are you running ZFS?
-
Yes, RAID 10 ZFS with no ARC, 6GB SAS drives.
-
Oh, I only had it when mounting with compose. I did resolve it by uaing fstab.
Oh well... I hoped you'd have a better solution. At least that works very well.
