Choose a VM size for compute nodes in an Azure Batch pool
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.
There are a few exceptions and limitations to choosing a VM size:
- Some VM series or VM sizes are not supported in Batch.
- Some VM sizes are restricted and need to be specifically enabled before they can be allocated.
Supported VM series and sizes
Pools in Virtual Machine configuration
Any promotional or preview VM sizes not listed aren't guaranteed for support.
|VM series||Supported sizes||Batch account pool allocation mode1|
|Basic A-series||All sizes except Basic_A0 (A0)||Any|
|A-series||All sizes except Standard_A0||Any|
|Dv2, Dsv2-series||All sizes||Any|
|Dv3, Dsv3-series||All sizes||Any|
|Memory optimized sizes||None||Not available|
|M-series||Standard_M64ms (low-priority only), Standard_M128s (low-priority only)||Any|
|NDv2-series||All sizes||User subscription mode|
|SAP HANA||None||Not available|
1 Some newer VM series are partially supported initially. These VM series can be allocated by Batch accounts with the pool allocation mode set to user subscription. See Manage Batch accounts for more information on Batch account configuration. See Quotas and limits to learn how to request quota for these partially supported VM series for user subscription Batch accounts.
2 These VM sizes can be allocated in Batch pools in Virtual Machine configuration, but you must request a specific quota increase.
Pools in Cloud Service configuration
Batch pools in the Cloud Service configuration support all VM sizes for Cloud Services except for the following:
|VM series||Unsupported sizes|
|Av2-series||Standard_A1_v2, Standard_A2_v2, Standard_A2m_v2|
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 or CUDA applications, consider specialized HPC or GPU-enabled VM sizes, respectively. (See Use RDMA-capable or GPU-enabled instances in Batch pools.)
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 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.
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.
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.
Pool configuration - In general, you have more VM size options when you create a pool in the Virtual Machine configuration, compared with the Cloud Service configuration.
- For an in-depth overview of Batch, see Develop large-scale parallel compute solutions with Batch.
- For information about using compute-intensive VM sizes, see Use RDMA-capable or GPU-enabled instances in Batch pools.