Which option was added to the load balancing calculatio…

Which option was added to the load balancing calculations of DRS in vSphere 6.5?

Which option was added to the load balancing calculations of DRS in vSphere 6.5?

A.
Network

B.
Memory

C.
Storage

D.
CPU

Explanation:
https://blogs.vmware.com/vsphere/2016/10/whats-new-in-vsphere-6-5-host-resource-managementand-operations.html

Show Hint

Leave a Reply 6

Your email address will not be published. Required fields are marked *

P2V

P2V

I think B is correct.

https://blogs.vmware.com/vsphere/2016/10/whats-new-in-vsphere-6-5-host-resource-management-and-operations.html

DRS Advanced Options
Memory Metric for Load Balancing: DRS uses Active memory + 25% as its primary metric when calculating memory load on a host. The Consumed memory vs active memory will cause DRS to use the consumed memory metric rather than Active. This is beneficial when memory is not over-allocated. As a side effect, the UI show the hosts be more balanced.

Reply

Ed

Ed

A is correct. C is incorrect because this is addressed in Storage DRS. CPU & Memory existed in previous versions of DRS.

Network-Aware DRS:

Traditionally, DRS has always considered the compute resource (CPU and memory) utilizations of hosts and
VMs for balancing load across hosts and placing VMs during power-on. This generally works well because in
many cases, CPU and memory are the most important resources needed for good application performance.
However, since network availability is not considered in this approach, sometimes this results in placing or
migrating a VM to a host which is already network saturated. This might have some performance impact on the
application if it happens to be network sensitive.

DRS is network-aware in vSphere 6.5, so it now considers the network utilization of host and network usage
requirements of VMs during initial placement and load balancing. This makes DRS load balancing and initial
placement of VMs more effective

Reply

broh

broh

https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/drs-vsphere65-perf.pdf

page. 13 ~15

New Additional Options
In order to simplify cluster management, in vSphere 6.5 three new options are exposed in the vSphere Web
Client, called Additional Options. These options provide simple customizations to DRS behavior to better suit
varied cluster needs. These additional options are pre-existing advanced cluster options with some predefined
settings.
These additional options are available, along with the existing configuration settings, in the
ClusterConfigurevSphere DRS in the vSphere Web Client (Figure 20).
VM Distribution
This additional option specifies DRS to consider distributing VMs evenly across hosts in the cluster for
availability purposes. While the primary goal of DRS is to ensure that all VMs are getting the resources they need
and that the load is balanced in the cluster, with this option, DRS will additionally try to ensure that the VM
spread (number of VMs per host) is even across the cluster. However, DRS will always prioritize load balancing
over the VM spread, so even distribution of VMs is done on a best-effort basis.
You can enable this option by selecting the corresponding check box under Additional Options in the vSphere
Web Client (Figure 21).

]Memory Metric for Load Balancing
DRS, by default, mainly considers the active memory usage for load balancing [1]. This additional option makes
DRS consider consumed memory usage, instead of active memory usage for load balancing. This option is
equivalent to setting the existing cluster advanced option PercentIdleMBInMemDemand with a value of 100.
You can enable this option by selecting the corresponding check box under Additional Options in the vSphere
Web Client (Figure 22).

CPU Over-Commitment
DRS supports over-committing physical resources for your VMs. This is very useful when you need to
consolidate your workloads for better utilization of hardware resources. This additional option lets you specify
the amount of CPU over-commitment as a percentage of total cluster CPU capacity that DRS should consider.
You can specify a minimum of 0 and a maximum of 500% over-commitment ratio. This additional option is
equivalent to using the pre-existing cluster advanced option MaxClusterCpuOvercommitPct.
You can enable this option by selecting the corresponding check box under Additional Options in the vSphere
Web Client, and by specifying the over-commitment percentage (Figure 23).
The additional DRS options provide more power to you. They simplify cluster management with easy-to-use
knobs in the vSphere Web Client.
Note that these additional options will override any equivalent cluster advanced options. For example, if you set
cluster advanced option PercentIdleMBInMemDemand to some value, and then enable the memory metric
option for load balancing, the advanced option will be cleared to give precedence to the new memory metric
option.

Reply