@Harvy66:
The importance of ECC is directly related to the importance to prevent or detect corruption. My home router does not need ECC. PFSense is an appliance, if it goes down, I can replace it. My file server is a different thing. If ZFS gets corrupted in the wrong place, assuming I have no backups, I can lose everything.
If you use PFSense in a HA setup, you may need ECC. If the master sustains corruption, that corruption could negatively affect the slave. Or even worse, the master limps along doing some really crazy stuff.
I've been working with computers for nearly 30 years now, since a weeee child. I've seen what bad memory can do. The oddest things. Maybe it makes your cursor look funny, maybe it makes your audio have periodic distortions, maybe it just makes the close button on all of your windows disappear. If you're lucky, your system crashes. If you're not lucky, some really strange pathological failure could occur, causing all kinds of havoc.
I completely agree with this.
My VM and NAS server definitely has ECC.
My little pfSense box? Not worth the hassle.
Back to Kaby Lake.
I just built a nice little Kaby Lake i3-7100 pfSense box based on this thread.
I am very happy with the results. No OpenVPN benchmarking yet. ahvent even installed pfSense yet, but I am already seriously impressed.
Idles at 6.2W at the wall, and maxes out at 46W with all threads (2C/4T@3.9Ghz) loaded in mprime.
Just stay away from the USB3 ports. pfSense doesn't seem to like those at all, and the installers will fail unless booted from one of the USB2 ports.