Previous generations of virtual machine sizes

This article provides information on previous generations of virtual machine sizes. These sizes can still be used, but there are newer generations available.

DS-series

ACU: 160

Size vCPU Memory: GiB Temp storage (SSD) GiB Max data disks Max cached and temp storage throughput: IOPS / MBps (cache size in GiB) Max uncached disk throughput: IOPS / MBps Max NICs / Expected network bandwidth (Mbps)
Standard_DS1 1 3.5 7 4 4,000 / 32 (43) 3,200 / 32 2 / 500
Standard_DS2 2 7 14 8 8,000 / 64 (86) 6,400 / 64 2 / 1000
Standard_DS3 4 14 28 16 16,000 / 128 (172) 12,800 / 128 4 / 2000
Standard_DS4 8 28 56 32 32,000 / 256 (344) 25,600 / 256 8 / 4000


DS-series - memory optimized

ACU: 160 1

Size vCPU Memory: GiB Temp storage (SSD) GiB Max data disks Max cached and temp storage throughput: IOPS / MBps (cache size in GiB) Max uncached disk throughput: IOPS / MBps Max NICs / Expected network bandwidth (Mbps)
Standard_DS11 2 14 28 8 8,000 / 64 (72) 6,400 / 64 2 / 1000
Standard_DS12 4 28 56 16 16,000 / 128 (144) 12,800 / 128 4 / 2000
Standard_DS13 8 56 112 32 32,000 / 256 (288) 25,600 / 256 8 / 4000
Standard_DS14 16 112 224 64 64,000 / 512 (576) 51,200 / 512 8 / 8000

1 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.

D-series

ACU: 160

Size vCPU Memory: GiB Temp storage (SSD) GiB Max temp storage throughput: IOPS / Read MBps / Write MBps Max data disks / throughput: IOPS Max NICs / Expected network bandwidth (Mbps)
Standard_D1 1 3.5 50 3000 / 46 / 23 4 / 4x500 2 / 500
Standard_D2 2 7 100 6000 / 93 / 46 8 / 8x500 2 / 1000
Standard_D3 4 14 200 12000 / 187 / 93 16 / 16x500 4 / 2000
Standard_D4 8 28 400 24000 / 375 / 187 32 / 32x500 8 / 4000


D-series - memory optimized

ACU: 160

Size vCPU Memory: GiB Temp storage (SSD) GiB Max temp storage throughput: IOPS / Read MBps / Write MBps Max data disks / throughput: IOPS Max NICs / Expected network bandwidth (Mbps)
Standard_D11 2 14 100 6000 / 93 / 46 8 / 8x500 2 / 1000
Standard_D12 4 28 200 12000 / 187 / 93 16 / 16x500 4 / 2000
Standard_D13 8 56 400 24000 / 375 / 187 32 / 32x500 8 / 4000
Standard_D14 16 112 800 48000 / 750 / 375 64 / 64x500 8 / 8000


A-series - compute-intensive instances

ACU: 225

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. This article provides information about the number of vCPUs, data disks, and NICs as well as storage throughput and network bandwidth for each size in this grouping.

Size vCPU Memory: GiB Temp storage (HDD): GiB Max data disks Max data disk throughput: IOPS Max NICs
Standard_A8 1 8 56 382 32 32x500 2
Standard_A9 1 16 112 382 64 64x500 4
Standard_A10 8 56 382 32 32x500 2
Standard_A11 16 112 382 64 64x500 4

1For MPI applications, dedicated RDMA backend network is enabled by FDR InfiniBand network, which delivers ultra-low-latency and high bandwidth.


A-series

ACU: 50-100

Size vCPU Memory: GiB Temp storage (HDD): GiB Max data disks Max data disk throughput: IOPS Max NICs / Expected network bandwidth (Mbps)
Standard_A0 1 1 0.768 20 1 1x500 2 / 100
Standard_A1 1 1.75 70 2 2x500 2 / 500
Standard_A2 2 3.5 135 4 4x500 2 / 500
Standard_A3 4 7 285 8 8x500 2 / 1000
Standard_A4 8 14 605 16 16x500 4 / 2000
Standard_A5 2 14 135 4 4x500 2 / 500
Standard_A6 4 28 285 8 8x500 2 / 1000
Standard_A7 8 56 605 16 16x500 4 / 2000


1 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.

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

Basic A

The basic tier sizes are primarily for development workloads and other applications that don't require load balancing, auto-scaling, or memory-intensive virtual machines.

Size – Size\Name vCPU Memory NICs (Max) Max temporary disk size Max. data disks (1023 GB each) Max. IOPS (300 per disk)
A0\Basic_A0 1 768 MB 2 20 GB 1 1x300
A1\Basic_A1 1 1.75 GB 2 40 GB 2 2x300
A2\Basic_A2 2 3.5 GB 2 60 GB 4 4x300
A3\Basic_A3 4 7 GB 2 120 GB 8 8x300
A4\Basic_A4 8 14 GB 2 240 GB 16 16x300

Size table definitions

  • 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.
  • If you want to get the best performance for your VMs, you should limit the number of data disks to 2 disks per vCPU.
  • Expected network bandwidth is the maximum aggregated bandwidth allocated per VM type across all NICs, for all destinations. Upper limits are not guaranteed, but are intended to provide guidance for selecting the right VM type for the intended application. Actual network performance will depend on a variety of factors including network congestion, application loads, and network settings. For information on optimizing network throughput, see Optimizing network throughput for Windows and Linux. To achieve the expected network performance on Linux or Windows, it may be necessary to select a specific version or optimize your VM. For more information, see How to reliably test for virtual machine throughput.

Other sizes

Next steps

Learn more about how Azure compute units (ACU) can help you compare compute performance across Azure SKUs.