I am going to follow-up with the conference by posting a couple of #ProTips that, according to participant feedback, were the most interesting to them from my talk. Here's the list:
- Disabling Delayed TCPIP Acknowledgements for Better iSCSI Performance
- Removing Removable Devices to Conserve CPU Cycles for Better Performance
- Single-Root I/O Virtualization (SR-IOV) on Cisco UCS for Better Performance Through VM-FEX
You can also read more about my vSphere 5.5 Performance Best Practices series that I did last April/May.
Use SR-IOV for Cisco UCS Maximum PErformance
Using the same amount of bandwidth, data sent using the Cisco virtual interface card (VIC) with Cisco Data Center VM-FEX uses 41 percent fewer CPU resources than the VMware vSwitch, freeing CPU cycles to deliver better application performance.
— Gaining Throughput with Data Center VM-FEX
Cisco® VM-FEX utilizes the capability to create multiple vNICs in combination with VMware VMDirectPath and Intel® VT-d technologies. This, in turn, allows the VMs to bypass the hypervisor for their networking connectivity by allowing direct access to the underlying adapter hardware. This approach avoids the overhead of the hypervisor software networking stack, resulting in lower system CPU utilization and higher networking throughput. — Cisco.com
- Cisco VM-FEX uses 16 percent lower system CPU for transmit and 30.4 percent lower system CPU for receive compared to VMware vSwitch for the same amount of bandwidth.
- Cisco VM-FEX uses 65.60 percent of system CPU for transmit and receive while driving 10.89 Gbps of bi-directional TCP network throughput compared to VMware vSwitch, which uses 81.60 percent of system CPU while driving only 7.97 Gbps.
- Cisco VM-FEX takes 36 percent less time for an average round trip compared to VMware vSwitch.
- Cisco VM-FEX offers over 40 percent reduction in latency, compared to VMware vSwitch
To sum up, VM-FEX is essentially captured by the Ford commercial series, "And is better":