Skip to content

Commit 29f52c4

Browse files
GitHubber17GitHubber17
authored
Merge pull request #78068 from laurenhughes/batch-vm-sizes
Batch VM sizes update
2 parents 569cdf0 + 2110754 commit 29f52c4

File tree

1 file changed

+41
-47
lines changed

1 file changed

+41
-47
lines changed

‎articles/batch/batch-pool-vm-sizes.md

Lines changed: 41 additions & 47 deletions
Original file line numberDiff line numberDiff line change
@@ -13,81 +13,75 @@ ms.workload:
1313
ms.tgt_pltfrm: na
1414
ms.devlang: na
1515
ms.topic: article
16-
ms.date: 01/25/2019
16+
ms.date: 05/28/2019
1717
ms.author: lahugh
1818
ms.custom: seodec18
1919

2020
---
21+
2122
# Choose a VM size for compute nodes in an Azure Batch pool
2223

2324
When you select a node size for an Azure Batch pool, you can choose from among almost all the VM sizes available in Azure. Azure offers a range of sizes for Linux and Windows VMs for different workloads.
2425

2526
There are a few exceptions and limitations to choosing a VM size:
2627

27-
* Some VM families or VM sizes are not supported in Batch.
28+
* Some VM series or VM sizes are not supported in Batch.
2829
* Some VM sizes are restricted and need to be specifically enabled before they can be allocated.
2930

30-
## Supported VM families and sizes
31+
## Supported VM series and sizes
3132

3233
### Pools in Virtual Machine configuration
3334

34-
Batch pools in the Virtual Machine configuration support all VM sizes ([Linux](../virtual-machines/linux/sizes.md), [Windows](../virtual-machines/windows/sizes.md)) *except* for the following:
35-
36-
| Family | Unsupported sizes |
37-
|---------|---------|
38-
| Basic A-series | Basic_A0 (A0) |
39-
| A-series | Standard_A0 |
40-
| B-series | All |
41-
| DC-series | All |
42-
| Extreme memory optimized | All |
43-
| Hb-series<sup>1,2</sup> | All |
44-
| Hc-series<sup>1,2</sup> | All |
45-
| Lsv2-series | All |
46-
| NDv2-series<sup>1,2</sup> | All |
47-
| NVv2-series<sup>1</sup> | All |
48-
| SAP HANA | All |
49-
50-
51-
<sup>1</sup> Planned for support.
52-
<sup>2</sup> Can be used by Batch accounts in user subscription mode; the user subscription mode Batch account needs to have the core quota set. See [configuration for user subscription mode](batch-account-create-portal.md#additional-configuration-for-user-subscription-mode) for more information.
53-
54-
The following VM sizes are supported only for low-priority nodes:
55-
56-
| Family | Supported sizes |
57-
|---------|---------|
58-
| M-series | Standard_M64ms |
59-
| M-series | Standard_M128s |
60-
61-
Other VM sizes in the M-series family are currently unsupported.
35+
Batch pools in the Virtual Machine configuration support almost all VM sizes ([Linux](../virtual-machines/linux/sizes.md), [Windows](../virtual-machines/windows/sizes.md)). See the following table to learn more about supported sizes and restrictions.
36+
37+
Any promotional or preview VM sizes not listed aren't guaranteed for support.
38+
39+
| VM series | Supported sizes | Allocation mode |
40+
|------------|---------|-----------------|
41+
| Basic A-series | All sizes *except* Basic_A0 (A0) | Any |
42+
| A-series | All sizes *except* Standard_A0 | Any |
43+
| Av2-series | All sizes | Any |
44+
| B-series | None | N/A |
45+
| DC-series | None | N/A |
46+
| Dv2, Dsv2-series | All sizes | Any |
47+
| Dv3, Dsv3-series | All sizes | Any |
48+
| [Memory optimized sizes](../virtual-machines/linux/sizes-memory.md) | None | N/A |
49+
| Fsv2-series | All sizes | Any |
50+
| H-series | All sizes | Any |
51+
| Hb-series | All sizes | User subscription mode |
52+
| Hc-series | All sizes | User subscription mode |
53+
| Ls-series | All sizes | Any |
54+
| Lsv2-series | None | N/A |
55+
| M-series | Standard_M64ms (low-priority only), Standard_M128s (low-priority only) | Any |
56+
| NCv2-series<sup>2</sup> | All sizes | Any |
57+
| NCv3-series<sup>2</sup> | All sizes | Any |
58+
| ND-series<sup>2</sup> | All sizes | Any |
59+
| NDv2-series | All sizes | User subscription mode |
60+
| NV-series | All sizes | Any |
61+
| NVv3-series | None | N/A |
62+
| SAP HANA | None | All |
63+
64+
<sup>1</sup> The ExtraSmall, Standard_A1_v2, Standard_A2_v2, and Standard_A2m_v2 sizes are not available in Cloud Services.
65+
<sup>2</sup> These VM sizes can be allocated in Batch pools in Virtual Machine configuration, but you must request a specific [quota increase](batch-quota-limit.md#increase-a-quota).
6266

6367
### Pools in Cloud Service configuration
6468

65-
Batch pools in the Cloud Service configuration support all [VM sizes for Cloud Services](../cloud-services/cloud-services-sizes-specs.md) *except* for the following:
69+
Batch pools in the Cloud Service configuration support all [VM sizes for Cloud Services](../cloud-services/cloud-services-sizes-specs.md) **except** for the following:
6670

67-
| Family | Unsupported sizes |
68-
|---------|---------|
69-
| A-series | ExtraSmall |
71+
| VM series | Unsupported sizes |
72+
|------------|-------------------|
73+
| A-series | Extra small |
7074
| Av2-series | Standard_A1_v2, Standard_A2_v2, Standard_A2m_v2 |
7175

72-
## Restricted VM families
73-
74-
The following VM families can be allocated in Batch pools, but you must request a specific quota increase (see [this article](batch-quota-limit.md#increase-a-quota)):
75-
76-
* NCv2-series
77-
* NCv3-series
78-
* ND-series
79-
80-
These sizes can only be used in pools in the Virtual Machine configuration.
81-
8276
## Size considerations
8377

8478
* **Application requirements** - Consider the characteristics and requirements of the application you'll run on the nodes. Aspects like whether the application is multithreaded and how much memory it consumes can help determine the most suitable and cost-effective node size. For multi-instance [MPI workloads](batch-mpi.md) or CUDA applications, consider specialized [HPC](../virtual-machines/linux/sizes-hpc.md) or [GPU-enabled](../virtual-machines/linux/sizes-gpu.md) VM sizes, respectively. (See [Use RDMA-capable or GPU-enabled instances in Batch pools](batch-pool-compute-intensive-sizes.md).)
8579

8680
* **Tasks per node** - It's typical to select a node size assuming one task runs on a node at a time. However, it might be advantageous to have multiple tasks (and therefore multiple application instances) [run in parallel](batch-parallel-node-tasks.md) on compute nodes during job execution. In this case, it is common to choose a multicore node size to accommodate the increased demand of parallel task execution.
8781

88-
* **Load levels for different tasks** - All of the nodes in a pool are the same size. If you intend to run applications with differing system requirements and/or load levels, we recommend that you use separate pools.
82+
* **Load levels for different tasks** - All of the nodes in a pool are the same size. If you intend to run applications with differing system requirements and/or load levels, we recommend that you use separate pools.
8983

90-
* **Region availability** - A VM family or size might not be available in the regions where you create your Batch accounts. To check that a size is available, see [Products available by region](https://azure.microsoft.com/regions/services/).
84+
* **Region availability** - A VM series or size might not be available in the regions where you create your Batch accounts. To check that a size is available, see [Products available by region](https://azure.microsoft.com/regions/services/).
9185

9286
* **Quotas** - The [cores quotas](batch-quota-limit.md#resource-quotas) in your Batch account can limit the number of nodes of a given size you can add to a Batch pool. To request a quota increase, see [this article](batch-quota-limit.md#increase-a-quota).
9387

0 commit comments

Comments
 (0)