This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Tuning Metric Weightings
XenCenter 2023.x.x is currently in preview and is not supported for production use. Note that any future references to production support apply only when XenCenter 2023.x.x and XenServer 8 go from preview status to general availability.
You can use XenCenter 2023.x.x to manage your XenServer 8 and Citrix Hypervisor 8.2 CU1 non-production environments. However, to manage your Citrix Hypervisor 8.2 CU1 production environment, use XenCenter 8.2.7. For more information, see the XenCenter 8.2.7 documentation.
You can install XenCenter 8.2.7 and XenCenter 2023.x.x on the same system. Installing XenCenter 2023.x.x does not overwrite your XenCenter 8.2.7 installation.
Workload Balancing uses metric weightings, a method of assigning importance to resources, to determine what hosts to optimize first.
Before tuning metric weightings, Citrix recommends reading about the optimization and consolidation process in the Workload Balancing documentation. The information in this article is a subset of that information and is only meant to be used as a reference when changing the user interface.
When Workload Balancing is processing optimization recommendations, it creates an optimization order. Workload Balancing determines the optimization order by ranking the hosts to address first according to which hosts have the highest metric values for whatever resource is ranked as the most important in the metric weightings page.
How Workload Balancing uses metric weightings when determining which hosts and VMs to process first varies according to the optimization mode, Maximum Density, or Maximum Performance. In general, metric weightings are used when a pool is in Maximum Performance mode. However, when Workload Balancing is in Maximum Density mode, it does use metric weightings if a resource exceeds its Critical threshold.
In Maximum Performance mode, Workload Balancing uses metric weightings to determine:
- Which hosts’ performance to address first
- Which VMs to recommend migrating first
For example, if you rank Network Writes as the most important resource, Workload Balancing first addresses performance issues and makes optimization recommendations for the host with the most Network Writes per second.
In Maximum Density mode, Workload Balancing only uses metric weightings when a host reaches the Critical threshold. Then Workload Balancing applies a Maximum Performance-like algorithm until no Hosts are exceeding the Critical thresholds. When using the Maximum Performance-like algorithm, Workload Balancing uses metric weightings to determine the optimization order in the same way as it does for Maximum Performance mode.
If two or more hosts have resources exceeding their Critical thresholds, Workload Balancing verifies the importance you set for each resource before determining which host to optimize first and which VMs on that host to relocate first.
For example, your pool contains Host A and Host B, which are in the following state:
- The CPU utilization on Host A exceeds the Critical threshold for CPU. The metric weighting for CPU utilization is set to the far right of the slider (More Important).
- The memory utilization on Host B exceeds the Critical threshold for memory. The metric weighting for memory utilization is set to the far left of the slider (Less Important).
Workload Balancing recommends optimizing Host A first because the resource on it that reached the Critical threshold is the resource assigned the highest weight. After Workload Balancing determines that it needs to address the performance on Host A, Workload Balancing then begins recommending placements for VMs on that host. These recommendations begin with the VM that has the highest CPU utilization, since that CPU utilization is the resource with the highest weight.
After Workload Balancing has recommended optimizing Host A, it makes optimization recommendations for Host B. When it recommends placements for the VMs on Host B, it does so by addressing CPU utilization first, since CPU utilization was assigned the highest weight.
If there are more hosts that need optimization, Workload Balancing addresses the performance on those hosts according to what host has the third highest CPU utilization.
By default, all metric weightings are set to the farthest point on the slider (More Important).
The weighting of metrics is relative. This behavior means that if all metrics are set to the same level, even if that level is Less Important, they are all weighted the same. The relation of the metrics to each other is more important than the actual weight at which you set each metric.
- Select the pool in the Resources pane, select the WLB tab, and then select Settings.
- In the left pane, select Metric Weighting.
In the Metric Weighting page, as desired, adjust the sliders beside the individual resources.
Moving the slider towards Less Important indicates that ensuring virtual machines always have the highest amount of this resource available is not as vital on this resource pool.
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.