Skip to content

Commit a8c8a38

Browse files
Merge pull request #278950 from rnautiyal/Autosclale
Update application-gateway-autoscaling-zone-redundant.md
2 parents ebd711a + eda0399 commit a8c8a38

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

articles/application-gateway/application-gateway-autoscaling-zone-redundant.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,11 +31,10 @@ Azure Application Gateways are always deployed in a highly available fashion. Th
3131

3232
Even if you configure autoscaling with zero minimum instances the service is still highly available, which is always included with the fixed price.
3333

34-
However, creating a new instance can take around six or seven minutes. If you don't want to have this downtime, you can configure a minimum instance count of two, ideally with Availability Zone support. This way you have at least two instances in your Azure Application Gateway under normal circumstances. So if one of them had a problem the other tries to handle the traffic while a new instance is being created. An Azure Application Gateway instance can support around 10 Capacity Units. Depending on how much traffic you typically have, you might want to configure your minimum instance autoscaling setting to a value higher than two.
34+
However, it’s important to note that provisioning a new instance may take approximately six to seven minutes. Understanding the scaling behavior of Application Gateway instances is key to maintaining performance under varying loads. These instances scale out in groups, and the group size is increased proactively when the current instance count is higher. This strategy allows the system to manage workload surges efficiently, preventing potential service disruptions or slowdowns. Each Azure Application Gateway instance can handle up to 10 Capacity Units. To optimize your autoscaling settings, consider your typical traffic patterns and set the minimum instances accordingly to ensure smooth operation.
3535

3636
For scale-in events, Application Gateway drains existing connections for 5 minutes on the instance that is subject for removal. After 5 minutes, existing connections are closed and the instance removed. Any new connections during or after the 5 minute scale-in time is established to other existing instances on the same gateway.
3737

38-
3938
## Next steps
4039

4140
- Learn how to [Schedule autoscaling for Application Gateway](application-gateway-externally-managed-scheduled-autoscaling.md)

0 commit comments

Comments
 (0)