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/batch/batch-pool-vm-sizes.md
+33-56Lines changed: 33 additions & 56 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Choose VM sizes and images for pools
3
3
description: How to choose from the available VM sizes and OS versions for compute nodes in Azure Batch pools
4
4
ms.topic: conceptual
5
-
ms.date: 09/02/2021
5
+
ms.date: 02/13/2023
6
6
ms.custom: seodec18
7
7
8
8
---
@@ -15,65 +15,33 @@ When you select a node size for an Azure Batch pool, you can choose from almost
15
15
16
16
### Pools in Virtual Machine configuration
17
17
18
-
Batch pools in the Virtual Machine configuration support almost all [VM sizes](../virtual-machines/sizes.md). The supported VM sizes in a region can be obtained via [Batch Management APIs](batch-apis-tools.md#batch-management-apis), as well as the [command line tools](batch-apis-tools.md#batch-command-line-tools) (PowerShell cmdlets and Azure CLI). For example, the [Azure Batch CLI command](/cli/azure/batch/location#az-batch-location-list-skus) to list supported VM sizes in a region is:
18
+
Batch pools in the Virtual Machine configuration support almost all [VM sizes](../virtual-machines/sizes.md) available in Azure.
19
+
The supported VM sizes in a region can be obtained via the Batch Management API. You can use one of the following methods to
20
+
return a list of VM sizes supported by Batch in a region:
For example, using the Azure CLI, you can obtain the list of skus for a particular Azure region with the following command:
19
27
20
28
```azurecli-interactive
21
-
az batch location list-skus --location
22
-
[--filter]
23
-
[--maxresults]
24
-
[--subscription]
29
+
az batch location list-skus --location <azure-region>
25
30
```
26
31
27
-
For each VM series, the following table also lists whether the VM series and VM sizes are supported by Batch.
28
-
29
-
| VM series | Supported sizes |
30
-
|------------|---------|
31
-
| Basic A | All sizes *except* Basic_A0 (A0) |
32
-
| A | All sizes *except* Standard_A0, Standard_A8, Standard_A9, Standard_A10, Standard_A11 |
33
-
| Av2 | All sizes |
34
-
| B | Not supported |
35
-
| DCsv2 | All sizes |
36
-
| Dv2, DSv2 | All sizes |
37
-
| Dv3, Dsv3 | All sizes |
38
-
| Dav4, Dasv4 | All sizes |
39
-
| Ddv4, Ddsv4 | All sizes |
40
-
| Dv4, Dsv4 | Not supported |
41
-
| Ev3, Esv3 | All sizes, except for E64is_v3 |
42
-
| Eav4, Easv4 | All sizes |
43
-
| Edv4, Edsv4 | All sizes |
44
-
| Ev4, Esv4 | Not supported |
45
-
| F, Fs | All sizes |
46
-
| Fsv2 | All sizes |
47
-
| FX<sup>1</sup> | All sizes |
48
-
| G, Gs | All sizes |
49
-
| H | All sizes |
50
-
| HB | All sizes |
51
-
| HBv2 | All sizes |
52
-
| HBv3 | All sizes |
53
-
| HC | All sizes |
54
-
| Ls | All sizes |
55
-
| Lsv2 | All sizes |
56
-
| M | All sizes |
57
-
| Mv2<sup>1</sup> | All sizes |
58
-
| NC | All sizes |
59
-
| NCv2 | All sizes |
60
-
| NCv3 | All sizes |
61
-
| NCasT4_v3 | All sizes |
62
-
| NC_A100_v4 | All sizes |
63
-
| ND | All sizes |
64
-
| NDv4 | All sizes |
65
-
| NDv2 | None - not yet available |
66
-
| NP | All sizes |
67
-
| NV | All sizes |
68
-
| NVv3 | All sizes |
69
-
| NVv4 | All sizes |
70
-
| SAP HANA | Not supported |
71
-
72
-
<sup>1</sup> These VM series can only be used with generation 2 VM Images.
32
+
> [!TIP]
33
+
> Batch **does not** support any VM SKU sizes that have only remote storage. A local temporary disk is required for Batch.
34
+
> For example, Batch supports [ddv4 and ddsv4](../virtual-machines/ddv4-ddsv4-series.md), but does not support
35
+
> [dv4 and dsv4](../virtual-machines/dv4-dsv4-series.md).
73
36
74
37
### Using Generation 2 VM Images
75
38
76
-
Some VM series, such as [Mv2](../virtual-machines/mv2-series.md), can only be used with [generation 2 VM images](../virtual-machines/generation-2.md). Generation 2 VM images are specified like any VM image, using the 'sku' property of the ['imageReference'](/rest/api/batchservice/pool/add#imagereference) configuration; the 'sku' strings have a suffix such as "-g2" or "-gen2". To get a list of VM images supported by Batch, including generation 2 images, use the ['list supported images'](/rest/api/batchservice/account/listsupportedimages) API, [PowerShell](/powershell/module/az.batch/get-azbatchsupportedimage), or [Azure CLI](/cli/azure/batch/pool/supported-images).
39
+
Some VM series, such as [FX](../virtual-machines/fx-series.md) and [Mv2](../virtual-machines/mv2-series.md), can only be used
40
+
with [generation 2 VM images](../virtual-machines/generation-2.md). Generation 2 VM images are specified like any VM image,
41
+
using the `sku` property of the [`imageReference`](/rest/api/batchservice/pool/add#imagereference) configuration; the `sku`
42
+
strings have a suffix such as `-g2` or `-gen2`. To get a list of VM images supported by Batch, including generation 2 images,
43
+
use the ['list supported images'](/rest/api/batchservice/account/listsupportedimages) API,
44
+
[PowerShell](/powershell/module/az.batch/get-azbatchsupportedimage), or [Azure CLI](/cli/azure/batch/pool/supported-images).
77
45
78
46
### Pools in Cloud Services Configuration
79
47
@@ -91,7 +59,7 @@ Batch pools in Cloud Services Configuration support all [VM sizes for Cloud Serv
91
59
92
60
-**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/sizes-hpc.md) or [GPU-enabled](../virtual-machines/sizes-gpu.md) VM sizes, respectively. For more information, see [Use RDMA-capable or GPU-enabled instances in Batch pools](batch-pool-compute-intensive-sizes.md).
93
61
94
-
-**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.
62
+
-**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's common to choose a multicore node size to accommodate the increased demand of parallel task execution.
95
63
96
64
-**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.
97
65
@@ -105,11 +73,20 @@ Batch pools in Cloud Services Configuration support all [VM sizes for Cloud Serv
105
73
106
74
Use one of the following APIs to return a list of Windows and Linux VM images currently supported by Batch, including the node agent SKU IDs for each image:
107
75
108
-
- Batch Service REST API: [List Supported Images](/rest/api/batchservice/account/listsupportedimages)
- Azure CLI: [az batch pool supported-images](/cli/azure/batch/pool/supported-images)
78
+
-[Batch Service APIs](batch-apis-tools.md#batch-service-apis): [List Supported Images](/rest/api/batchservice/account/listsupportedimages)
79
+
80
+
For example, using the Azure CLI, you can obtain the list of supported VM images with the following command:
81
+
82
+
```azurecli-interactive
83
+
az batch pool supported-images list
84
+
```
111
85
112
-
It is strongly recommended to avoid images with impending Batch support end of life (EOL) dates. These dates can be discovered via the [`ListSupportedImages` API](/rest/api/batchservice/account/listsupportedimages), [PowerShell](/powershell/module/az.batch/get-azbatchsupportedimage), or [Azure CLI](/cli/azure/batch/pool/supported-images). Please see the [Batch best practices guide](best-practices.md) for more information regarding Batch pool VM image selection.
86
+
It's recommended to avoid images with impending Batch support end of life (EOL) dates. These dates can be discovered via
87
+
the [`ListSupportedImages` API](/rest/api/batchservice/account/listsupportedimages),
88
+
[PowerShell](/powershell/module/az.batch/get-azbatchsupportedimage), or [Azure CLI](/cli/azure/batch/pool/supported-images).
89
+
For more information, see the [Batch best practices guide](best-practices.md) regarding Batch pool VM image selection.
0 commit comments