You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machine-scale-sets/standby-pools-faq.md
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,16 +17,22 @@ ms.reviewer: ju-shim
17
17
Get answers to frequently asked questions about standby pools for Virtual Machine Scale Sets in Azure.
18
18
19
19
### What are standby pools for Virtual Machine Scale Sets?
20
-
Azure standby pools is a feature for Virtual Machine Scale Sets with Flexible Orchestration that enables faster scaling out of resources by creating a pool of pre-provisioned virtual machines ready to service your workload.
20
+
Azure standby pools for Virtual Machine Scale Sets with Flexible Orchestration enables faster scaling out of resources by creating a pool of pre-provisioned virtual machines ready to service your workload.
21
21
22
22
### When should I use standby pools for Virtual Machine Scale Sets?
23
23
Using a standby pool with your Virtual Machine Scale Set can help improve scale-out performance by completing various pre and post provisioning steps in the pool before the instances are placed into the scale set.
24
24
25
25
### What are the benefits of using Azure standby pools for Virtual Machine Scale Sets?
26
-
Standby pools is a powerful feature for accelerating your time to scale-out and reducing the management needed for provisioning virtual machine resources and getting them ready to service your workload. If your applications are latency sensitive or have long initialization steps, standby pools can help with reducing that time and managing the steps to make your virtual machines ready on your behalf.
26
+
Standby pools is a powerful feature for accelerating your time to scaleout and reducing the management needed for provisioning virtual machine resources and getting them ready to service your workload. If your applications are latency sensitive or have long initialization steps, standby pools can help with reducing that time and managing the steps to make your virtual machines ready on your behalf.
27
27
28
28
### Can I use standby pools on Virtual Machine Scale Sets with Uniform Orchestration?
29
-
Standby pools is only supported on Virtual Machine Scale Sets with Flexible Orchestration.
29
+
Standby pools are only supported on Virtual Machine Scale Sets with Flexible Orchestration.
30
+
31
+
### Does using a standby pool guarantee capacity?
32
+
Using a standby pool with deallocated instances doesn't guarantee capacity. When starting the deallocated virtual machine, there needs to be enough capacity in the region your instances are deployed in to start the machines. If using running virtual machines in your pool, those virtual machines are already allocated and consuming compute capacity. When the virtual machine moves from the standby pool to the Virtual Machine Scale Set, it doesn't release the compute resources and doesn't require any additional allocation of resources.
33
+
34
+
### How long can my standby pool name be?
35
+
A standby pool can be anywhere between 3 and 24 characters. For more information, see [Resource naming restrictions for Azure resources](..//azure-resource-manager/management/resource-name-rules.md)
30
36
31
37
### Can I use standby pools for Virtual Machine Scale Sets if I'm already using Azure autoscale?
32
38
Attaching a standby pool to a Virtual Machine Scale Set with Azure autoscale enabled isn't supported.
0 commit comments