Sizes for virtual machines in Azure

This article describes the available sizes and options for the Azure virtual machines you can use to run your Linux apps and workloads. It also provides deployment considerations to be aware of when you're planning to use these resources. This article is also available for Windows virtual machines.

Important


There are multiple standard sizes to choose from on Azure. Considerations for some of these sizes include:

  • D-series VMs are designed to run applications that demand higher compute power and temporary disk performance. D-series VMs provide faster processors, a higher memory-to-core ratio, and a solid-state drive (SSD) for the temporary disk. For details, see the announcement on the Azure blog, New D-Series Virtual Machine Sizes.
  • Dv2-series, a follow-on to the original D-series, features a more powerful CPU. The Dv2-series CPU is about 35% faster than the D-series CPU. It is based on the latest generation 2.4 GHz Intel Xeon® E5-2673 v3 (Haswell) processor, and with the Intel Turbo Boost Technology 2.0, can go up to 3.1 GHz. The Dv2-series has the same memory and disk configurations as the D-series.
  • F-series is based on the 2.4 GHz Intel Xeon® E5-2673 v3 (Haswell) processor, which can achieve clock speeds as high as 3.1 GHz with the Intel Turbo Boost Technology 2.0. This is the same CPU performance as the Dv2-series of VMs. At a lower per-hour list price, the F-series is the best value in price-performance in the Azure portfolio based on the Azure Compute Unit (ACU) per core.

    The F-series also introduces a new standard in VM size naming for Azure. For this series and VM sizes released in the future, the numeric value after the family name letter will match the number of CPU cores. Additional capabilities, such as optimized for premium storage, will be designated by letters following the numeric CPU core count. This naming format will be used for future VM sizes released but will not retroactively change the names of any existing VM sizes which have been released.

  • G-series VMs offer the most memory and run on hosts that have Intel Xeon E5 V3 family processors.
  • DS-series, DSv2-series, Fs-series and GS-series VMs can use Premium Storage, which provides high-performance, low-latency storage for I/O intensive workloads. These VMs use solid-state drives (SSDs) to host a virtual machine’s disks and also provide a local SSD disk cache. Premium Storage is available in certain regions. For details, see Premium Storage: High-performance storage for Azure virtual machine workloads.
  • The A-series and Av2-series VMs can be deployed on a variety of hardware types and processors. The size is throttled, based upon the hardware, to offer consistent processor performance for the running instance, regardless of the hardware it is deployed on. To determine the physical hardware on which this size is deployed, query the virtual hardware from within the Virtual Machine.
  • The A0 size is over-subscribed on the physical hardware. For this specific size only, other customer deployments may impact the performance of your running workload. The relative performance is outlined below as the expected baseline, subject to an approximate variability of 15 percent.

The size of the virtual machine affects the pricing. The size also affects the processing, memory, and storage capacity of the virtual machine. Storage costs are calculated separately based on used pages in the storage account. For details, see Virtual Machines Pricing Details and Azure Storage Pricing.

The following considerations might help you decide on a size:

  • The A8-A11 and H-series sizes are also known as compute-intensive instances. The hardware that runs these sizes is designed and optimized for compute-intensive and network-intensive applications, including high-performance computing (HPC) cluster applications, modeling, and simulations. The A8-A11 series uses Intel Xeon E5-2670 @ 2.6 GHZ and the H-series uses Intel Xeon E5-2667 v3 @ 3.2 GHz. For detailed information and considerations about using these sizes, see About the H-series and compute-intensive A-series VMs.
  • Dv2-series, D-series, G-series, and the DS/GS counterparts are ideal for applications that demand faster CPUs, better local disk performance, or have higher memory demands. They offer a powerful combination for many enterprise-grade applications.
  • The F-series VMs are an excellent choice for workloads that demand faster CPUs but do not need as much memory or local SSD per CPU core. Workloads such as analytics, gaming servers, web servers, and batch processing will benefit from the value of the F-series.
  • Some of the physical hosts in Azure data centers may not support larger virtual machine sizes, such as A5 – A11. As a result, you may see the error message Failed to configure virtual machine or Failed to create virtual machine when resizing an existing virtual machine to a new size; creating a new virtual machine in a virtual network created before April 16, 2013; or adding a new virtual machine to an existing cloud service. See Error: “Failed to configure virtual machine” on the support forum for workarounds for each deployment scenario.
  • Your subscription might also limit the number of cores you can deploy in certain size families. To increase a quota, contact Azure Support.

Performance considerations

We have created the concept of the Azure Compute Unit (ACU) to provide a way of comparing compute (CPU) performance across Azure SKUs. This will help you easily identify which SKU is most likely to satisfy your performance needs. ACU is currently standardized on a Small (Standard_A1) VM being 100 and all other SKUs then represent approximately how much faster that SKU can run a standard benchmark.

Important

The ACU is only a guideline. The results for your workload may vary.


SKU Family ACU/Core
Standard_A0 50
Standard_A1-4 100
Standard_A5-7 100
Standard_A1-8v2 100
Standard_A2m-8mv2 100
A8-A11 225*
D1-14 160
D1-15v2 210 - 250*
DS1-14 160
DS1-15v2 210-250*
F1-F16 210-250*
F1s-F16s 210-250*
G1-5 180 - 240*
GS1-5 180 - 240*
H 290 - 300*

ACUs marked with a * use Intel® Turbo technology to increase CPU frequency and provide a performance boost. The amount of the boost can vary based on the VM size, workload, and other workloads running on the same host.

Size tables

The following tables show the sizes and the capacities they provide.

  • Storage capacity is shown in units of GiB or 1024^3 bytes. When comparing disks measured in GB (1000^3 bytes) to disks measured in GiB (1024^3) remember that capacity numbers given in GiB may appear smaller. For example, 1023 GiB = 1098.4 GB
  • Disk throughput is measured in input/output operations per second (IOPS) and MBps where MBps = 10^6 bytes/sec.
  • Data disks can operate in cached or uncached modes. For cached data disk operation, the host cache mode is set to ReadOnly or ReadWrite. For uncached data disk operation, the host cache mode is set to None.
  • Maximum network bandwidth is the maximum aggregated bandwidth allocated and assigned per VM type. The maximum bandwidth provides guidance for selecting the right VM type to ensure adequate network capacity is available. When moving between Low, Moderate, High and Very High, the throughput will increase accordingly. Actual network performance will depend on many factors including network and application loads, and application network settings.

A-series

Size CPU cores Memory: GiB Local HDD: GiB Max data disks Max data disk throughput: IOPS Max NICs / Network bandwidth
Standard_A0 1 0.768 20 1 1x500 1 / low
Standard_A1 1 1.75 70 2 2x500 1 / moderate
Standard_A2 2 3.5 135 4 4x500 1 / moderate
Standard_A3 4 7 285 8 8x500 2 / high
Standard_A4 8 14 605 16 16x500 4 / high
Standard_A5 2 14 135 4 4X500 1 / moderate
Standard_A6 4 28 285 8 8x500 2 / high
Standard_A7 8 56 605 16 16x500 4 / high


A-series - compute-intensive instances

For information and considerations about using these sizes, see About the H-series and compute-intensive A-series VMs.

Size CPU cores Memory: GiB Local HDD: GiB Max data disks Max data disk throughput: IOPS Max NICs / Network bandwidth
Standard_A8* 8 56 382 16 16x500 2 / high
Standard_A9* 16 112 382 16 16x500 4 / very high
Standard_A10 8 56 382 16 16x500 2 / high
Standard_A11 16 112 382 16 16x500 4 / very high

*RDMA capable


Av2-series

Size CPU cores Memory: GiB Local SSD: GiB Max data disks Max data disk throughput: IOPS Max NICs / Network bandwidth
Standard_A1_v2 1 2 10 2 2x500 1 / moderate
Standard_A2_v2 2 4 20 4 4x500 2 / moderate
Standard_A4_v2 4 8 40 8 8x500 4 / high
Standard_A8_v2 8 16 80 16 16x500 8 / high
Standard_A2m_v2 2 16 20 4 4X500 2 / moderate
Standard_A4m_v2 4 32 40 8 8x500 4 / high
Standard_A8m_v2 8 64 80 16 16x500 8 / high

D-series

Size CPU cores Memory: GiB Local SSD: GiB Max data disks Max data disk throughput: IOPS Max NICs / Network bandwidth
Standard_D1 1 3.5 50 2 2x500 1 / moderate
Standard_D2 2 7 100 4 4x500 2 / high
Standard_D3 4 14 200 8 8x500 4 / high
Standard_D4 8 28 400 16 16x500 8 / high
Standard_D11 2 14 100 4 4x500 2 / high
Standard_D12 4 28 200 8 8x500 4 / high
Standard_D13 8 56 400 16 16x500 8 / high
Standard_D14 16 112 800 32 32x500 8 / very high


Dv2-series

Size CPU cores Memory: GiB Local SSD: GiB Max data disks Max data disk throughput: IOPS Max NICs / Network bandwidth
Standard_D1_v2 1 3.5 50 2 2x500 1 / moderate
Standard_D2_v2 2 7 100 4 4x500 2 / high
Standard_D3_v2 4 14 200 8 8x500 4 / high
Standard_D4_v2 8 28 400 16 16x500 8 / high
Standard_D5_v2 16 56 800 32 32x500 8 / extremely high
Standard_D11_v2 2 14 100 4 4x500 2 / high
Standard_D12_v2 4 28 200 8 8x500 4 / high
Standard_D13_v2 8 56 400 16 16x500 8 / high
Standard_D14_v2 16 112 800 32 32x500 8 / extremely high
Standard_D15_v2 20 140 1,000 40 40x500 8 / extremely high*

*In some regions, accelerated networking is available for the Standard_D15_v2 size. For more information about usage and availability, see Accelerated Networking is in Preview and Accelerated Networking for a virtual machine.


DS-series*

Size CPU cores Memory: GiB Local SSD: GiB Max data disks Max cached disk throughput: IOPS / MBps (cache size in GiB) Max uncached disk throughput: IOPS / MBps Max NICs / Network bandwidth
Standard_DS1 1 3.5 7 2 4,000 / 32 (43) 3,200 / 32 1 / moderate
Standard_DS2 2 7 14 4 8,000 / 64 (86) 6,400 / 64 2 / high
Standard_DS3 4 14 28 8 16,000 / 128 (172) 12,800 / 128 4 / high
Standard_DS4 8 28 56 16 32,000 / 256 (344) 25,600 / 256 8 / high
Standard_DS11 2 14 28 4 8,000 / 64 (72) 6,400 / 64 2 / high
Standard_DS12 4 28 56 8 16,000 / 128 (144) 12,800 / 128 4 / high
Standard_DS13 8 56 112 16 32,000 / 256 (288) 25,600 / 256 8 / high
Standard_DS14 16 112 224 32 64,000 / 512 (576) 51,200 / 512 8 / very high

MBps = 10^6 bytes per second, and GiB = 1024^3 bytes.

*The maximum disk throughput (IOPS or MBps) possible with a DS series VM may be limited by the number, size and striping of the attached disk(s). For details, see Premium Storage: High-performance storage for Azure virtual machine workloads.


DSv2-series*

Size CPU cores Memory: GiB Local SSD: GiB Max data disks Max cached disk throughput: IOPS / MBps (cache size in GiB) Max uncached disk throughput: IOPS / MBps Max NICs / Network bandwidth
Standard_DS1_v2 1 3.5 7 2 4,000 / 32 (43) 3,200 / 48 1 moderate
Standard_DS2_v2 2 7 14 4 8,000 / 64 (86) 6,400 / 96 2 high
Standard_DS3_v2 4 14 28 8 16,000 / 128 (172) 12,800 / 192 4 high
Standard_DS4_v2 8 28 56 16 32,000 / 256 (344) 25,600 / 384 8 high
Standard_DS5_v2 16 56 112 32 64,000 / 512 (688) 51,200 / 768 8 extremely high
Standard_DS11_v2 2 14 28 4 8,000 / 64 (72) 6,400 / 96 2 high
Standard_DS12_v2 4 28 56 8 16,000 / 128 (144) 12,800 / 192 4 high
Standard_DS13_v2 8 56 112 16 32,000 / 256 (288) 25,600 / 384 8 high
Standard_DS14_v2 16 112 224 32 64,000 / 512 (576) 51,200 / 768 8 extremely high
Standard_DS15_v2 20 140 280 40 80,000 / 640 (720) 64,000 / 960 8 extremely high**

MBps = 10^6 bytes per second, and GiB = 1024^3 bytes.

*The maximum disk throughput (IOPS or MBps) possible with a DSv2 series VM may be limited by the number, size and striping of the attached disk(s). For details, see Premium Storage: High-performance storage for Azure virtual machine workloads.

**In some regions, accelerated networking is available for the Standard_DS15_v2 size. For more information about usage and availability, see Accelerated Networking is in Preview and Accelerated Networking for a virtual machine.


F-series

Size CPU cores Memory: GiB Local SSD: GiB Max data disks Max disk throughput: IOPS Max NICs / Network bandwidth
Standard_F1 1 2 16 2 2x500 1 / moderate
Standard_F2 2 4 32 4 4x500 2 / high
Standard_F4 4 8 64 8 8x500 4 / high
Standard_F8 8 16 128 16 16x500 8 / high
Standard_F16 16 32 256 32 32x500 8 / extremely high


Fs-series*

Size CPU cores Memory: GiB Local SSD: GiB Max data disks Max cached disk throughput: IOPS / MBps (cache size in GiB) Max uncached disk throughput: IOPS / MBps Max NICs / Network bandwidth
Standard_F1s 1 2 4 2 4,000 / 32 (12) 3,200 / 48 1 / moderate
Standard_F2s 2 4 8 4 8,000 / 64 (24) 6,400 / 96 2 / high
Standard_F4s 4 8 16 8 16,000 / 128 (48) 12,800 / 192 4 / high
Standard_F8s 8 16 32 16 32,000 / 256 (96) 25,600 / 384 8 / high
Standard_F16s 16 32 64 32 64,000 / 512 (192) 51,200 / 768 8 / extremely high

MBps = 10^6 bytes per second, and GiB = 1024^3 bytes.

*The maximum disk throughput (IOPS or MBps) possible with a Fs series VM may be limited by the number, size and striping of the attached disk(s). For details, see Premium Storage: High-performance storage for Azure virtual machine workloads.


G-series

Size CPU cores Memory: GiB Local SSD: GiB Max data disks Max disk throughput: IOPS Max NICs / Network bandwidth
Standard_G1 2 28 384 4 4 x 500 1 / high
Standard_G2 4 56 768 8 8 x 500 2 / high
Standard_G3 8 112 1,536 16 16 x 500 4 / very high
Standard_G4 16 224 3,072 32 32 x 500 8 / extremely high
Standard_G5 32 448 6,144 64 64 x 500 8 / extremely high


GS-series*

Size CPU cores Memory: GiB Local SSD: GiB Max data disks Max cached disk throughput: IOPS / MBps (cache size in GiB) Max uncached disk throughput: IOPS / MBps Max NICs / Network bandwidth
Standard_GS1 2 28 56 4 10,000 / 100 (264) 5,000 / 125 1 / high
Standard_GS2 4 56 112 8 20,000 / 200 (528) 10,000 / 250 2 / High
Standard_GS3 8 112 224 16 40,000 / 400 (1,056) 20,000 / 500 4 / very high
Standard_GS4 16 224 448 32 80,000 / 800 (2,112) 40,000 / 1,000 8 / extremely high
Standard_GS5 32 448 896 64 160,000 / 1,600 (4,224) 80,000 / 2,000 8 / extremely high

MBps = 10^6 bytes per second, and GiB = 1024^3 bytes.

*The maximum disk throughput (IOPS or MBps) possible with a GS series VM may be limited by the number, size and striping of the attached disk(s).


H-series

Azure H-series virtual machines are the next generation high performance computing VMs aimed at high end computational needs, like molecular modeling, and computational fluid dynamics. These 8 and 16 core VMs are built on the Intel Haswell E5-2667 V3 processor technology featuring DDR4 memory and local SSD based storage.

In addition to the substantial CPU power, the H-series offers diverse options for low latency RDMA networking using FDR InfiniBand and several memory configurations to support memory intensive computational requirements.

For information and considerations about using these sizes, see About the H-series and compute-intensive A-series VMs.

Size CPU cores Memory: GiB Local SSD: GiB Max data disks Max disk throughput: IOPS Max NICs / Network bandwidth
Standard_H8 8 56 1000 16 16 x 500 2 / high
Standard_H16 16 112 2000 32 32 x 500 4 / very high
Standard_H8m 8 112 1000 16 16 x 500 2 / high
Standard_H16m 16 224 2000 32 32 x 500 4 / very high
Standard_H16r* 16 112 2000 32 32 x 500 4 / very high
Standard_H16mr* 16 224 2000 32 32 x 500 4 / very high

*RDMA capable


N-series

The NC and NV sizes are also known as GPU-enabled instances. These are specialized virtual machines that include NVIDIA's GPU cards, optimized for different scenarios and use cases. The NV sizes are optimized and designed for remote visualization, streaming, gaming, encoding and VDI scenarios utilizing frameworks such as OpenGL and DirectX. The NC sizes are more optimized for compute-intensive and network-intensive applications and algorithms, including CUDA- and OpenCL-based applications and simulations.

NV instances

The NV instances are powered by NVIDIA’s Tesla M60 GPU card and NVIDIA GRID for desktop accelerated applications and virtual desktops where customers will be able to visualize their data or simulations. Users will be able to visualize their graphics intensive workflows on the NV instances to get superior graphics capability and additionally run single precision workloads such as encoding and rendering. The Tesla M60 delivers 4096 CUDA cores in a dual-GPU design with up to 36 streams of 1080p H.264.

Size CPU cores Memory: GiB Local SSD: GiB GPU
Standard_NV6 6 56 380 1
Standard_NV12 12 112 680 2
Standard_NV24 24 224 1440 4

1 GPU = one-half M60 card.

Supported operating systems

NC instances

The NC instances are powered by NVIDIA’s Tesla K80 card. Users can now crunch through data much faster by leveraging CUDA for energy exploration applications, crash simulations, ray traced rendering, deep learning and more. The Tesla K80 delivers 4992 CUDA cores with a dual-GPU design, up to 2.91 Teraflops of double-precision and up to 8.93 Teraflops of single-precision performance.

Size CPU cores Memory: GiB Local SSD: GiB GPU
Standard_NC6 6 56 380 1
Standard_NC12 12 112 680 2
Standard_NC24 24 224 1440 4
Standard_NC24r* 24 224 1440 4

1 GPU = one-half K80 card.

*RDMA capable

Supported operating systems


Notes: Standard A0 - A4 using CLI and PowerShell

In the classic deployment model, some VM size names are slightly different in CLI and PowerShell:

  • Standard_A0 is ExtraSmall
  • Standard_A1 is Small
  • Standard_A2 is Medium
  • Standard_A3 is Large
  • Standard_A4 is ExtraLarge

Next steps