Switched from Hyper-V 2012 R2 to VMware 6…
-
Just a comment post…
I had my pfSense running on Hyper-V 2012 R2. Everything worked, but it seemed like there was more latency on the network traffic. I tried measuring it various different ways, but wasn't ever able to prove it with data.
In any case, I needed to setup an ESXi 6.0 server for testing anyway, so I created a new pfSense VM there and imported the configuration, and I have to say it runs much better.
By better I mean web pages load quicker, and with the same traffic and packages/filtering, the VMware VM uses right at 1/3 the CPU.
I have a feeling Hyper-V wasn't playing nicely with my Intel I210 NICs, but am not sure if that was a driver thing or a Hyper-V thing. But I do know that the interrupt CPU utilization was much higher on Hyper-V than it is on ESXi.
Jason
-
Curious on vsphere whether you did vmxnet3 or e1000 nics. I just did a vsphere pfsense install and went e1000 but wondered whether I should re-do with vmxnet3.
-
I used vmxnet3. I did not try it with e1000 or e1000e - although I probably should sometime if I get a free few minutes.
-
I have switched back to e1000 from vmx3 - even though freebsd has native support now. I don't like that it only shows autoselect for speed and was giving errors with cdp reporting half duplex.. While e1000 works fine and don't have these issues.
I use the ladvd package to have pfsense report via cdp and lldp, etc..
While there is most like a bit of performance benefit with using vmx3 over the e1000, not an issue for me since only routing traffic for home network with a 50/10 internet connection. While I wish it could have more bandwidth between segments. The testing I did between vmx3 and e1000 was so small better to get my cdp and lldp info
