@provels said in ZFS on SSD RAID10 efficiency:
@sergei_shablovsky Have you tried running
systat -iostat
to see if you even have any bottlenecks?
Need to remind that is NOT situation where some bottlenecks already limiting overall pfSense performance or create some kind of problems.
Till now I collecting info (by LibreNMS, Prometheus and ELK) about how exactly which type of workload impact on server’s hardware resources consuming.
To be prepared for situation when workload spontaneously rapidly growing.
In my mind, I think RAM for /var and /tmp and proc cores/GHz are the most important, followed by a disk redundancy strategy like a mirror set.
My initial question was about FreeBSD and pfSense FINE TUNING and
Also need to saying the time are running, FreeBSD changing (and pfSense+ version already using 15-CURRENT, but pfSense CE - still on 14-CURRENT), additional pfSense’s packages updated,… so IMPACTS ON DISK SUBSYSTEM are changing accordingly…
So periodically need to re-tuning both pfSense and FreeBSD.
After that, I'd opt for server redundancy/cold spare.
Of coarse, HA would be implemented.
You're already shipping the logs to another server anyway.