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 families 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 families and sizes
Pools in Virtual Machine configuration
|Basic A-series||Basic_A0 (A0)|
|Extreme memory optimized||All|
1 Planned for support.
2 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 for more information.
The following VM sizes are supported only for low-priority nodes:
Other VM sizes in the M-series family are currently unsupported.
Pools in Cloud Service configuration
Batch pools in the Cloud Service configuration support all VM sizes for Cloud Services except for the following:
|Av2-series||Standard_A1_v2, Standard_A2_v2, Standard_A2m_v2|
Restricted VM families
The following VM families can be allocated in Batch pools, but you must request a specific quota increase (see this article):
These sizes can only be used in pools in the Virtual Machine configuration.
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 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.
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.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.