OPENZFS NFS FULL
OPENZFS NFS PC

There are still lots of cheap intel optane 16gb sticks on ebay which work great for basic needs. Do note that even using the fastest possible storage will not make sync writes as fast as non-sync writes, there’s just an unavoidable and rather large performance loss for data safety. If you temporarily turn off sync writes and lie about it then you can determine if having an SLOG would actually benefit you in real conditions. NFS by default makes sync writes, which is where the awful performance comes from when writing to it. The real solution to problems solved by L2ARC is generally to max out ram first. Unless you are willing to dig into analyzing your ARC hit/miss ratio, ignore it. L2ARC on benefits special workloads, which most consumers simply don’t have. I use Netdata for all monitoring, so In case you have some idea on which graphs I should look at…Īnyway, thanks for reading, every response and also for your ideas!.I thought about reducing the raid_02 size and adding SLOG / L2ARC on them - any thoughts regarding this?.Any idea how I could improve the NFS performance inside my vms?.

Do you see general problems, which need to be addressed?.

Adding “async” does not affect the performance.Īll vms are connected to the server using an virtual network and virtio devices - so the only limit should be the cpu?! All NFS shares are mounted using “defaults,_netdev,tomount,x-systemd.requires=network-online.target” as options. I assume something is going wrong on the ZFS side, as NFS is managed by it.

OPENZFS NFS PC

I have only simple copy-paste benchmarks for now, but peak write performance feels slow (my pc 1GB/s → ssh → vm → nfs → root server → zfs: ~50MB/s) while the direct performance is way better (my pc 1GB/s → ssh → root server → zfs: ~120MB/s). I’ve then changed the backup schedules to more spread out over the hour and this problem is now “gone” - but still the performance of the NFS attached data sets are still not impressive. As one can imagine this caused all the gameservers to lag as hell and freeze for several seconds - often timing out the players on them.

OPENZFS NFS FULL

Until recently they all ran their backups (which basically copies the whole server) simultaneously starting every full hour. I have currently about 8 active Minecraft servers on the vm called “Gameserver-1”.

I use Pterodactyl for hosting my game servers - it also provides a handy service to create backups for the servers. The vms root disks are all located on the raid_02 pool (inside a shared data set), the raid_01 is my general data pool (there are also the game server files located).Īll pool have lz4 compression enabled and are tuned to pass trough any TRIM events from the vms (yes, there are two minor data disks also located on raid_01 - not relevant). I’ve got different vms for different purposes - two for different isolated docker environments (trusted and public), two gameserver vms (one with NFS storage, one which stores everything on its disk) and some others (not relevant today (?)). All vms can access the ZFS data sets using NFS (over an internal virtio-network). This all is done using the host only as ZFS system & hypervisor and than running everything inside their own libvirtd-vms.

ZFS “raid_02”, 3x1TB WD Red SSD (RAID5).

ZFS “raid_01”, 3x2TB WD Red HDD (RAID5).

So today’s topic is my server, which runs a broad spectrum of different services - starting with GitLab (CI), Jellyfin, web sites and also many game servers (all this just an excerpt).