-
-
-
Collect a Citrix Diagnostic Facility (CDF) Trace at System Startup
-
Load balance machines
-
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à))
Translation failed!
Load balance machines
Note:
You can manage your Citrix Virtual Apps and Desktops deployment using two management consoles: Web Studio (web-based) and Citrix Studio (Windows-based). This feature is available only in Web Studio.
This feature applies to all your catalogs — single-session OS or multi-session OS catalogs. Vertical load balancing applies only to multi-session OS machines.
Load balancing can be configured at the site level and at the delivery group level. You have two options: vertical and horizontal. By default, horizontal load balancing is enabled.
Load balancing settings at site level
-
Vertical load balancing. Assigns an incoming user session to the most loaded machine that has not yet reached the maximum load. This saturates existing machines before moving on to new machines. Users disconnecting from existing machines free up capacity on those machines. Incoming loads are then assigned to those machines. Vertical load balancing degrades the user experience but reduces costs (sessions maximize powered-on machine capacity).
Example: You have two machines configured for 10 sessions each. The first machine handles the first 10 concurrent sessions. The second machine handles the eleventh session.
Tip:
To specify the maximum number of sessions a machine can host, use the Maximum number of sessions policy setting.
Alternatively, you can use PowerShell to enable or disable vertical load balancing site-wide. Use the
UseVerticalScalingForRdsLaunches
setting in theSet-BrokerSite
cmdlet. UseGet-BrokerSite
to display the value of theUseVerticalScalingForRdsLaunches
setting. See the cmdlet help for details. -
Horizontal load balancing. Assigns an incoming user session to the least-loaded, powered-on machine available. Horizontal load balancing improves the user experience but increases costs (because more machines are kept powered on). By default, horizontal load balancing is enabled.
Example: You have two machines configured for 10 sessions each. The first machine handles five concurrent sessions. The second machine also handles five.
To configure this feature, from Manage > Full Configuration, select Settings in the left pane. Select an option under Load balance multi-session catalogs.
Load balancing settings at delivery group level
Configuring load balancing at the delivery group level allows you to override the load balancing settings inherited from the site level. You can achieve maximum utilization for each machine when you select vertical load balancing at the delivery group level. This will help reduce costs in public clouds. This configuration can be done during the creation of a new delivery group or editing an existing delivery group.
Horizontal load balancing. Sessions are distributed among powered-on machines. For example, if you have two machines configured for 10 sessions each, the first machine handles five concurrent sessions and the second machine also handles five.
Vertical load balancing. Sessions maximize powered-on machine capacity and save machine costs. For example, if you have two machines configured for 10 sessions each, the first machine handles the first 10 concurrent sessions. The second machine handles the eleventh session.
Share
Share
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.