compdigit44
asked on
VM Setting Latency sensitivity
Our environment consist of a vCenter 6 Update 3 server and 110 ESXi 6 Update 2 hosts. There is a setting on VMs for "Latency Sensitivity". If I am understanding thing correctly. When using this setting it take your total CPU and memory assignment and creates reservations of the same value. VMs can be migrated with this setting in place as long as the target host has ample resources. What other value does this latency sensitivity setting provide?
ASKER
We have a VM that is VOIP related and teh vendors is requesting this setting. Just to be clear the VM can or cannot be vmotioned when set to high? What does manually setting the reservation vs using the latency setting by us?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We have DRS set for manual only so at least it can be moved it need be... Thanks again
Okay, well you can check what will be moved before hitting Run!
Don't trust DRS (Automatic yet!)
Don't trust DRS (Automatic yet!)
there is a whitepaper here, relevant to 5.5...
https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/latency-sensitive-perf-vsphere55-white-paper.pdf
It's only when set to HIGH, does it change CPU and Memory reservations.
Also DRS is latency sensitive aware, and tries to pin VMs on the same host and not move them using a soft-affinity rule, to pin to that host. As a vMotion can cause latency issues