For example, if four VMs share a single disk and actively use it, each VM can yield only 25 percent of the bandwidth of that disk. Placing VMs with highly disk-intensive workloads on different physical disks will likely improve overall performance. Consider these requirements when you select storage controllers and disks and choose the RAID configuration. The storage hardware should have sufficient I/O bandwidth and capacity to meet current and future needs of the VMs that the physical server hosts.
To reduce the CPU usage of network I/Os from VMs, Hyper-V can use hardware offloads such as Large Send Offload (LSOv1), TCPv4 checksum offload, Chimney, and VMQ.įor details on network hardware considerations, see “Performance Tuning for the Networking Subsystem” earlier in this guide. When hosting multiple VMs, using multiple network adapters allows for distribution of the network traffic among the adapters for better overall performance. Each network adapter is assigned to its own virtual switch, allowing each virtual switch to service a subset of virtual machines. If the expected loads are network intensive, the virtualization server can benefit from having multiple network adapters or multiport network adapters. Having additional memory available allows the root to efficiently perform I/Os on behalf of the VMs and operations such as a VM snapshot. Hyper-V first allocates the memory for child partitions, which should be sized based on the needs of the expected load for each VM. The physical server requires sufficient memory for the root and child partitions. Hyper-V can benefit from larger processor caches, especially for loads that have a large working set in memory and in VM configurations in which the ratio of virtual processors to logical processors is high. These features allow for better energy efficiency over previous versions of Hyper-V. Hyper-V in Windows Server 2008 R2 adds support for deep CPU idle states, timer coalescing, core parking, and guest idle state. You can achieve additional run-time efficiency by using processors that support Second Level Address Translation (SLAT) technologies such as EPT or NPT. Hyper-V in Windows Server 2008 R2 presents the logical processors as one or more virtual processors to each active virtual machine. For more information, refer to “Choosing and Tuning Server Hardware” earlier in this guide. The hardware considerations for Hyper-V servers generally resemble those of non-virtualized servers, but Hyper-V servers can exhibit increased CPU usage, consume more memory, and need larger I/O bandwidth because of server consolidation. This section describes best practices for selecting hardware for virtualization servers and installing and setting up Windows Server 2008 R2 for the Hyper-V server role. Correct Memory Sizing for Root Partition.Correct Memory Sizing for Child Partitions.
0 kommentar(er)
