VMware vSphere 6.7性能优化最佳实践全解析

需积分: 10 130 浏览量更新于2024-07-15 收藏 1.32MB PDF 举报

《VMware vSphere 6.7性能最佳实践》是一本专门针对VMware vSphere 6.7的性能优化指南，它提供了在部署和管理vSphere环境中至关重要的性能技巧。该书并非全面的规划和配置手册，而是着重于帮助用户解决在虚拟化平台上的关键性能瓶颈问题。书中涵盖了vSphere ESXi 6.7（vSphere的计算基础架构）和vCenter Server 6.7（用于管理和监控集群的中心控制台）的优化建议。首先，关于本书，它发布于2018年7月27日，由VMware, Inc.编撰，提供了最新技术文档的链接，以及用户可以获取产品更新和支持反馈的渠道。所有内容受到美国和国际版权法的保护，并可能受到多项专利的保护。书中提及的“VMware”、“vSphere boxes”标志、Virtual SMP（模拟多处理器）和VMotion（虚拟机迁移）是VMware的注册商标。本书的核心内容包括： 1. **硬件选择与验证**：章节介绍了选择支持vSphere 6.7的最佳硬件配置，包括处理器、内存、存储和网络组件。这部分将涵盖硬件兼容性、性能需求以及如何确保硬件能够满足虚拟环境的高可用性和性能要求。 2. **性能监控与调整**：着重讲解如何使用vCenter Server的内置工具进行性能监控，识别性能瓶颈，如CPU使用率、内存占用、磁盘I/O等，并提供调整策略以提升整体系统效率。 3. **虚拟机优化**：针对虚拟机配置提供最佳实践，包括合理的内存分配、CPU预留和份额设置，以及如何利用动态资源调度（DRS）和Distributed Resource Scheduler（DRS）来平衡负载。 4. **存储性能**：涵盖了不同类型的存储（如SAN、NAS、vSAN等）的优化方法，包括数据存储布局、缓存策略以及使用快照和复制服务的最佳实践。 5. **网络架构**：介绍如何设计和配置高效网络架构，包括虚拟交换机（Vswitch）、网络I/O控制和流量管理，以保证虚拟机间的通信性能。 6. **虚拟机模板和一致性**：强调了使用性能优化的模板创建虚拟机的重要性，以及如何通过设置一致性模式（Consistency Mode）来减少虚拟机启动时间。 7. **高可用性和容灾**：讨论了如何在性能和灾备之间取得平衡，包括使用HA（High Availability）和DRS以实现故障转移和资源优化。 8. **安全与性能**：探讨了安全设置对性能的影响，如何实施安全策略而不牺牲性能，例如最小化不必要的安全检查和使用最新的安全补丁。总结来说，《VMware vSphere 6.7性能最佳实践》是一份实用的参考手册，旨在帮助管理员通过理解和应用这些策略，提高vSphere环境的整体性能，降低运维成本，同时确保系统的稳定性和可靠性。对于任何希望在vSphere 6.7环境中获得最佳性能表现的用户，这本书都是不可或缺的资源。

VMware, Inc. 15

Chapter 1 Hardware for Use with VMware vSphere

 Applications or systems that write large amounts of data to storage, such as data acquisition or

transaction logging systems, should not share Ethernet links to a storage device with other applications

or systems. These types of applications perform best with dedicated connections to storage devices.

 For iSCSI and NFS, make sure that your network topology does not contain Ethernet bottlenecks, where

multiple links are routed through fewer links, potentially resulting in oversubscription and dropped

network packets. Any time a number of links transmitting near capacity are switched to a smaller number

of links, such oversubscription is a possibility.

Recovering from these dropped network packets results in large performance degradation. In addition to

time spent determining that data was dropped, the retransmission uses network bandwidth that could

otherwise be used for new transactions.

 Be aware that with software-initiated iSCSI and NFS the network protocol processing takes place on the

host system, and thus these might require more CPU resources than other storage options.

 Local storage performance might be improved with write-back cache. If your local storage has write-back

cache installed, make sure it’s enabled and contains a functional battery module. For more information,

see VMware KB article 1006602.

 Make sure storage adapter cards are installed in slots with enough bandwidth to support their expected

throughput. Be careful to distinguish between similar-sounding—but potentially incompatible—bus

architectures, including PCI, PCI-X, PCI Express (PCIe), and PCIe 3.0 (aka PCIe Gen3), and be sure to note

the number of “lanes” for those architectures that can support more than one width.

For example, in order to supply their full bandwidth potential, single-port 32Gb/s Fibre Channel HBA

cards would need to be installed in at least PCIe Gen2 x8 or PCIe Gen3 x4 slots (either of which is capable

of a net maximum of 32Gb/s in each direction) and dual-port 32Gb/s Fibre Channel HBA cards would

need to be installed in at least PCIe Gen3 x8 slots (which are capable of a net maximum of 64Gb/s in each

direction).

These high-performance cards will typically function just as well in slower PCIe slots, but their maximum

throughput could be limited by the slots’ available bandwidth. This is most relevant for workloads that

make heavy use of large block size I/Os, as this is where these cards tend to develop their highest

throughput.

Performance Best Practices for VMware vSphere 6.7

16 VMware, Inc.

Hardware Networking Considerations

 Before undertaking any network optimization effort, you should understand the physical aspects of the

network. The following are just a few aspects of the physical layout that merit close consideration:

 Consider using server-class network interface cards (NICs) for the best performance.

 Make sure the network infrastructure between the source and destination NICs doesn’t introduce

bottlenecks. For example, if both NICs are 10Gb/s, make sure all cables and switches are capable of

the same speed and that the switches are not configured to a lower speed.

 For the best networking performance, we recommend the use of network adapters that support the

following features:

 Checksum offload

 TCP segmentation offload (TSO)

 Ability to handle high-memory DMA (that is, 64-bit DMA addresses)

 Ability to handle multiple Scatter Gather elements per Tx frame

 Jumbo frames (JF)

 Large receive offload (LRO)

 Receive Side Scaling (RSS)

 When using a virtualization encapsulation protocol, such as VXLAN or GENEVE:

 The NICs should support offload of that protocol’s encapsulated packets.

 The NICs should support NetQueue and, along with it, inner (encapsulated) MAC and VXLAN

Network ID (VNI) filtering.

 Make sure network cards are installed in slots with enough bandwidth to support their maximum

throughput. As described in “Hardware Storage Considerations” on page 13, be careful to distinguish

between similar-sounding—but potentially incompatible—bus architectures.

Ideally single-port 10Gb/s Ethernet network adapters should use PCIe x8 (or higher) or PCI-X 266 and

dual-port 10Gb/s Ethernet network adapters should use PCIe x16 (or higher). There should preferably be

no “bridge chip” (e.g., PCI-X to PCIe or PCIe to PCI-X) in the path to the actual Ethernet device (including

any embedded bridge chip on the device itself), as these chips can reduce performance.

Ideally 40Gb/s Ethernet network adapters should use PCI Gen3 x8/x16 slots (or higher).

Multiple physical network adapters between a single virtual switch (vSwitch) and the physical network

constitute a NIC team. NIC teams can provide passive failover in the event of hardware failure or network

outage and, in some configurations, can increase performance by distributing the traffic across those

physical network adapters.

When using load balancing across multiple physical network adapters connected to one vSwitch, all the

NICs should have the same line speed.

If the physical network switch (or switches) to which your physical NICs are connected support Link

Aggregation Control Protocol (LACP), configuring both the physical network switches and the vSwitch

to use this feature can increase throughput and availability.

VMware, Inc. 17

Chapter 1 Hardware for Use with VMware vSphere

Hardware BIOS Settings

The default hardware BIOS settings on servers might not always be the best choice for optimal performance.

This section lists some of the BIOS settings you might want to check, particularly when first configuring a new

server.

General BIOS Settings

 Make sure you are running the latest version of the BIOS available for your system.

 Make sure the BIOS is set to enable all populated processor sockets and to enable all cores in each socket.

 Enable “Turbo Boost” in the BIOS if your processors support it.

 Make sure hyper-threading is enabled in the BIOS for processors that support it.

 Some NUMA-capable systems provide an option in the BIOS to disable NUMA by enabling node

interleaving. In most cases you will get the best performance by disabling node interleaving (in other

words, leaving NUMA enabled).

 Make sure any hardware-assisted virtualization features (VT-x, AMD-V, EPT, RVI, and so on) are enabled

in the BIOS.

 Disable from within the BIOS any devices you won’t be using. This might include, for example, unneeded

serial, USB, or network ports. See “ESXi General Considerations” on page 19 for further details.

 If the BIOS allows the memory scrubbing rate to be configured, we recommend leaving it at the

manufacturer’s default setting.

 If your hardware supports AES-NI (see “AES-NI Support” on page 12), and your deployment will be able

to make use of the feature (see “vSphere Virtual Machine Encryption Recommendations” on page 35,

“VMware vMotion Recommendations” on page 65, and “VMware vSAN” on page 81):

 Make sure your BIOS version supports AES-NI (in some cases a BIOS upgrade might be required for

AES-NI support)

 Make sure AES-NI is enabled in BIOS.

Power Management BIOS Settings

VMware ESXi includes a full range of host power management capabilities in the software that can save power

when a host is not fully utilized (see “Host Power Management in ESXi” on page 23). We recommend that you

configure your BIOS settings to allow ESXi the most flexibility in using (or not using) the power management

features offered by your hardware, and that you then make your power-management choices within ESXi.

 In order to allow ESXi to control CPU power-saving features, set power management in the BIOS to “OS

Controlled Mode” or equivalent. Even if you don’t intend to use these power-saving features, ESXi

provides a convenient way to manage them.

 C1E is a hardware-managed state; when ESXi puts the CPU into the C1 state, the CPU hardware can

determine, based on its own criteria, to deepen the state to C1E. Availability of the C1E halt state typically

provides a reduction in power consumption with little or no impact on performance.

OTE Because of the large number of different server models and configurations, the BIOS options discussed

below might not be comprehensive for your server.

NOTE After updating the BIOS you should revisit your BIOS settings in case new BIOS options become

available or the settings of old options have changed.

OTE After changes are made to these hardware-assisted virtualization features, some systems might

need a complete power down before the changes take effect. See

http://communities.vmware.com/docs/DOC-8978 for details.

剩余87页未读，继续阅读

qq_31713265

粉丝: 0
资源: 17

VMware vSphere 6.7性能优化最佳实践全解析

VMware ESXi 5.1命令行界面入门

Vmware vSphere5的命令行界面入门指南

vsphere-esxi-vcenter-server-51用户文档

vsphere-esxi-vcenter-server-70-setup-wsfc.pdf

nvidia-grid-vsphere-6.7-510.47.03-511.65.zip

nvidia-grid-vsphere-7.0-510.73.06-510.73.08-512.78

vmware-esxi-7.0u1-16850804-depot.zip

vmw-esxi-7.0.3-metadata

vmware esxi 如何开启vCenter Server服务

vmware 服务器虚拟化部署流程

最新资源