This topic provides guidance about how to modify the default Critical thresholds and how values set for Critical threshold alter High, Medium, and Low thresholds.
This information is only provided for reference while changing thresholds. To understand the concepts discussed in this topic, it is important to read them in the fuller context of the information provided in the Workload Balancing Administrator's Guide.
When evaluating utilization, Workload Balancing compares its daily average to four thresholds: low, medium, high, and critical. After you specify (or accept the default) critical threshold, Workload Balancing sets the other thresholds relative to the critical threshold on a pool. You might want to change Critical thresholds as a way of controlling when optimization recommendations are triggered.
Workload Balancing evaluates CPU, Memory, Network Read and Network Write utilization for physical hosts in a resource pool.
For more information, see the Workload Balancing Administrator's Guide.
Workload Balancing determines whether or not to produce recommendations based on if the averaged historical utilization for a resource violates its threshold. As discussed in the Workload Balancing Administrator's Guide, Workload Balancing recommendations are triggered when the High threshold in Maximum Performance mode or Low and Critical thresholds for Maximum Density mode are violated. After you specify a new Critical threshold for a resource, Workload Balancing resets the resource's other thresholds relative to the new Critical threshold. (To simplify the user interface, the Critical threshold is the only threshold you can change through XenCenter.)
This means that if you increase, for example, the pool's Critical threshold for CPU Utilization to 95%, Workload Balancing automatically resets the High, Medium, and Low thresholds to 80.75%, 47.5%, and 23.75% respectively.
To perform this calculation for a specific threshold, multiply the factor for the threshold with the value you entered for the critical threshold for that resource:
High, Medium, or Low Threshold = Critical Threshold * Threshold Factor
For example, if you change the Critical threshold for Network Reads to 40MB/sec and you want to know its Low threshold, you multiply 40 by 0.25, which equals 10MB/sec. To obtain the Medium threshold, you multiple 40 by 0.50, and so on.
To prevent the pool master from becoming overloaded, Workload Balancing automatically sets the pool master's Critical Thresholds at lower values.
While the Critical threshold triggers many recommendations, other thresholds can also trigger recommendations, as follows:
Maximum Density. When a metric value drops below the Low threshold, it signals Workload Balancing that hosts are being underutilized and triggers an optimization recommendation to consolidate virtual machines on fewer hosts. Workload Balancing continues to recommend moving virtual machines onto a host until the metric values for one of the host's resource reaches its High threshold.
However, if after a virtual machine is relocated, a resource's utilization on the virtual machine's new host exceeds its Critical threshold, Workload Balancing will temporarily use an algorithm similar to the Maximum Performance load-balancing algorithm to find a new host for the virtual machines. Workload Balancing continues to use this algorithm to recommend moving virtual machines until resource utilization on hosts across the pool falls below the High threshold.
In Critical Thresholds page, accept or enter a new value in the Critical Thresholds boxes. Workload Balancing uses these thresholds when making virtual-machine placement and pool-optimization recommendations. Workload Balancing strives to keep resource utilization on a host below the critical values set.