|
1 | 1 | ---
|
2 | 2 | title: Azure Virtual Desktop host pool load-balancing - Azure
|
3 |
| -description: Learn about host pool load-balancing methods for a Azure Virtual Desktop environment. |
| 3 | +description: Learn about host pool load-balancing algorithms for a Azure Virtual Desktop environment. |
4 | 4 | author: Heidilohr
|
5 | 5 | ms.topic: conceptual
|
6 | 6 | ms.date: 10/12/2020
|
7 | 7 | ms.author: helohr
|
8 | 8 | manager: femila
|
9 | 9 | ---
|
10 |
| -# Host pool load-balancing methods |
| 10 | +# Host pool load-balancing algorithms |
11 | 11 |
|
12 | 12 | >[!IMPORTANT]
|
13 | 13 | >This content applies to Azure Virtual Desktop with Azure Resource Manager Azure Virtual Desktop objects. If you're using Azure Virtual Desktop (classic) without Azure Resource Manager objects, see [this article](./virtual-desktop-fall-2019/host-pool-load-balancing-2019.md).
|
14 | 14 |
|
15 |
| -Azure Virtual Desktop supports two load-balancing methods. Each method determines which session host will host a user's session when they connect to a resource in a host pool. |
| 15 | +Azure Virtual Desktop supports two load-balancing algorithms. Each algorithm determines which session host will host a user's session when they connect to a resource in a host pool. |
16 | 16 |
|
17 |
| -The following load-balancing methods are available in Azure Virtual Desktop: |
| 17 | +The following load-balancing algorithms are available in Azure Virtual Desktop: |
18 | 18 |
|
19 | 19 | - Breadth-first load balancing allows you to evenly distribute user sessions across the session hosts in a host pool.
|
20 | 20 | - Depth-first load balancing allows you to saturate a session host with user sessions in a host pool. Once the first session host reaches its session limit threshold, the load balancer directs any new user connections to the next session host in the host pool until it reaches its limit, and so on.
|
21 | 21 |
|
22 |
| -Each host pool can only configure one type of load-balancing specific to it. However, both load-balancing methods share the following behaviors no matter which host pool they're in: |
| 22 | +Each host pool can only configure one type of load-balancing specific to it. However, both load-balancing algorithms share the following behaviors no matter which host pool they're in: |
23 | 23 |
|
24 |
| -- If a user already has a session in the host pool and is reconnecting to that session, the load balancer will successfully redirect them to the session host with their existing session. This behavior applies even if that session host's AllowNewConnections property is set to False. |
| 24 | +- If a user already has an active or disconnected session in the host pool and signs in again, the load balancer will successfully redirect them to the session host with their existing session. This behavior applies even if that session host's AllowNewConnections property is set to False (drain mode is enabled). |
25 | 25 | - If a user doesn't already have a session in the host pool, then the load balancer won't consider session hosts whose AllowNewConnections property is set to False during load balancing.
|
26 | 26 |
|
27 |
| -## Breadth-first load-balancing method |
| 27 | +## Breadth-first load-balancing algorithm |
28 | 28 |
|
29 |
| -The breadth-first load-balancing method allows you to distribute user connections to optimize for this scenario. This method is ideal for organizations that want to provide the best experience for users connecting to their pooled virtual desktop environment. |
| 29 | +The breadth-first load-balancing algorithm allows you to distribute user sessions across session hosts to optimize for session performance. This algorithm is ideal for organizations that want to provide the best experience for users connecting to their pooled virtual desktop environment. |
30 | 30 |
|
31 |
| -The breadth-first method first queries session hosts that allow new connections. The method then selects a session host randomly from half the set of session hosts with the least number of sessions. For example, if there are nine machines with 11, 12, 13, 14, 15, 16, 17, 18, and 19 sessions, a new session you create won't automatically go to the first machine. Instead, it can go to any of the first five machines with the lowest number of sessions (11, 12, 13, 14, 15). |
| 31 | +The breadth-first algorithm first queries session hosts that allow new connections. The algorithm then selects a session host randomly from half the set of session hosts with the least number of sessions. For example, if there are nine machines with 11, 12, 13, 14, 15, 16, 17, 18, and 19 sessions, a new session you create won't automatically go to the first machine. Instead, it can go to any of the first five machines with the lowest number of sessions (11, 12, 13, 14, 15). |
32 | 32 |
|
33 |
| -## Depth-first load-balancing method |
| 33 | +## Depth-first load-balancing algorithm |
34 | 34 |
|
35 |
| -The depth-first load-balancing method allows you to saturate one session host at a time to optimize for this scenario. This method is ideal for cost-conscious organizations that want more granular control on the number of virtual machines they've allocated for a host pool. |
| 35 | +The depth-first load-balancing algorithm allows you to saturate one session host at a time to optimize for scale down scenarios. This algorithm is ideal for cost-conscious organizations that want more granular control on the number of virtual machines they've allocated for a host pool. |
36 | 36 |
|
37 |
| -The depth-first method first queries session hosts that allow new connections and haven't gone over their maximum session limit. The method then selects the session host with highest number of sessions. If there's a tie, the method selects the first session host in the query. |
| 37 | +The depth-first algorithm first queries session hosts that allow new connections and haven't gone over their maximum session limit. The algorithm then selects the session host with highest number of sessions. If there's a tie, the algorithm selects the first session host in the query. |
38 | 38 |
|
39 | 39 | >[!IMPORTANT]
|
40 | 40 | >The depth-first load balancing algorithm distributes sessions to session hosts based on the maximum session host limit. This parameter is required when you use the depth-first load balancing algorithm. For the best possible user experience, make sure to change the maximum session host limit parameter to a number that best suits your environment.
|
0 commit comments