So, if low CPU utilization is required then SR-IOV is your best bet. SR-IOV is not needed for bandwidth, as the Hyper-V VM bus can saturate a 10 Gb Ethernet connection, but it uses up about a CPU core for the calculations. If you're going to use SR-IOV extensively, be aware that NICs that support it today are limited in the number of virtual functions they can provide some give only four, some 32, some up to 64 per NIC. When you have a server that supports SR-IOV in BIOS, as well as an SR-IOV-capable NIC, it presents Virtual Functions - essentially, these are virtual copies of itself - to VMs. SR-IOV is the same shift of network functions from software to hardware for increased performance and flexibility. This is now known as Intel-VT and AMD-V and is a requirement for most modern hypervisors. In the early days of hypervisor virtualization, Intel and AMD realized that they could help provide better performance by offloading certain functions from software onto the processors themselves. Perhaps one of the most interesting additions to the arsenal of network enhancements in Windows Server 2012, SR-IOV has specific uses and limitations that it pays to be aware of when planning new Hyper-V clusters.
0 Comments
Leave a Reply. |