Bug #9463
closed
Extremely Slow Performance with Chelsio NICs on Hyper-V (Only Pfsense Impacted)
Added by Taylor Higley over 6 years ago.
Updated over 6 years ago.
Affected Architecture:
amd64
Description
I have a multi-node Hyper-V cluster, each with an Intel X540 10G NIC and a Chelsio T540-BT 10G NIC. The Intel NICs are in their own VM Switch and the Chelsio NICs are in a separate VM Switch.
The performance of pfSense when attached to the VM Switch using the Chelsio NICs - as measured with iperf and real-world usage - is horrible (approximately 50Kbps). Switching the same pfSense instances to the VM Switch using Intel results in 7+Gbps of throughput.
To rule out the Chelsio NICs themselves, I ran multiple tests. Both Windows virtual machines and non-pfSense FreeBSD 11.2 VMs can push 7+Gbps without an issue on the same vSwitch where pfSense instances are getting under 1Mbps. This has been replicated across several pfSense instances, including a fresh install of 2.4.4-p2.
I have played with VMQ on/off, SR-IOV on/off, and the pfSense offload options (every variation of the three checkboxes) without any improvement. Given that FreeBSD 11.2 seems to work perfectly on the exact same setup, it seems like this may be a bug in pfSense.
Files
- Status changed from New to Not a Bug
If pfSense is connected to a virtual switch it has no way to know what kind of network adapter is tied into that switch in Hyper-V. This is almost certainly not a pfSense bug, but something between Hyper-V, that NIC, and your virtual switch. Could be settings, a bug, or something else in your environment or even VM settings, but not a guest OS problem.
Thanks for the reply. In theory, I entirely understand where you are coming from. What I am struggling with significantly here though is that, on the exact same VM Switch, NIC, host, etc. FreeBSD 11.2 or Windows performs at full wire speed while a fresh pfSense installation (created just for the sake of sanity) is literally 50Kb/sec. With no other variable different except the Guest OS, it really leaves me at a dead-end of sorts.
Jim Pingle wrote:
If pfSense is connected to a virtual switch it has no way to know what kind of network adapter is tied into that switch in Hyper-V. This is almost certainly not a pfSense bug, but something between Hyper-V, that NIC, and your virtual switch. Could be settings, a bug, or something else in your environment or even VM settings, but not a guest OS problem.
Also available in: Atom
PDF
Updated by 
Updated by