Microsoft Azure excited to announce the general availability of our new Dv3 VM sizes. Azure also changing the naming for the high memory D sizes (D11-D14) to become the Ev3 family. These new sizes introduce Hyper-Threading Technology running on the Intel® Broadwell E5-2673 v4 2.3GHz processor, and the Intel® Haswell 2.4 GHz E5-2673 v3. The shift from physical cores to virtual CPU’s (vCPU) is a key architectural change that enables us to unlock the full potential of the latest processors to support even larger VM sizes. By unlocking more power from the underlying hardware, Azure able to harness better performance and efficiency, resulting in cost savings that we are passing on to our customers. These new Hyper-Threaded sizes will be priced up to 28% lower than the previous Dv2 sizes.
The Dv3 and Ev3 sizes are also some of the first VM’s to be running on Windows Server 2016 hosts. Windows 2016 hosts enable Nested Virtualization and Hyper-V Containers for these new VM sizes. Nested virtualization allows you to run a Hyper-V server on an Azure virtual machine. With nested virtualization you can run a Hyper-V Container in a virtualized container host, set-up a Hyper-V lab in a virtualized environment, or to test multi-machine scenarios. You can find more information on Nested Virtualization on Azure.
Azure new Dv3 VM sizes are a good balance of memory to vCPU performance, with up to 64 vCPU’s and 256GiB of RAM. Our newly named Ev3 sizes provide you with more memory to vCPU than the Dv3, so you can run larger workloads on sizes up to our largest E64 size, with 64 vCPUs and 432GiB of RAM.
The current Dv2, DSv2, F, Fs and Av2 sizes, with the exception of our DS15v2 and the D15v2, will also be available on our new Intel® Broadwell processors. The D15v2 and DS15v2 sizes are dedicated to our Intel® Haswell processors.
| Size | vCPU’s | Memory: GiB |
Local SSD: GiB |
Max data disks | Max local disk throughput: IOPS / Read MBps / Write MBps |
Max NICs / Network bandwidth |
| Standard_D2_v3 | 2 | 8 | 50 | 4 | 3000/46/23 | 2 / moderate |
| Standard_D4_v3 | 4 | 16 | 100 | 8 | 6000/93/46 | 2 / moderate |
| Standard_D8_v3 | 8 | 32 | 200 | 16 | 12000/187/93 | 4 / high |
| Standard_D16_v3 | 16 | 64 | 400 | 32 | 24000/375/187 | 8 / high |
| Standard_E2_v3 | 2 | 16 | 50 | 4 | 3000/46/23 | 2 / moderate |
| Standard_E4_v3 | 4 | 32 | 100 | 8 | 6000/93/46 | 2 / moderate |
| Standard_E8_v3 | 8 | 64 | 200 | 16 | 12000/187/93 | 4 / high |
| Standard_E16_v3 | 16 | 128 | 400 | 32 | 24000/375/187 | 8 / high |
| Standard_E32_v3 | 32 | 256 | 800 | 32 | 48000/750/375 | 8 / extremely high |
| Standard_E64_v3 | 64 | 432 | 1600 | 32 | 96000/1000/500 | 8 / extremely high |
| Size | vCPU’s | Memory: GiB | Local SSD: GiB | Max data disks | Max cached and local disk throughput: IOPS / MBps (cache size in GiB) | Max uncached disk throughput: IOPS / MBps | Max NICs / Expected network performance (Mbps) |
| Standard_D2s_v3 | 2 | 8 | 16 | 4 | 4,000 / 32 (50) | 3,200 / 48 | 2 / moderate |
| Standard_D4s_v3 | 4 | 16 | 32 | 8 | 8,000 / 64 (100) | 6,400 / 96 | 2 / moderate |
| Standard_D8s_v3 | 8 | 32 | 64 | 16 | 16,000 / 128 (200) | 12,800 / 192 | 4 / high |
| Standard_D16s_v3 | 16 | 64 | 128 | 32 | 32,000 / 256 (400) | 25,600 / 384 | 8 / high |
| Standard_E2s_v3 | 2 | 16 | 32 | 4 | 4,000 / 32 (50) | 3,200 / 48 | 2 / moderate |
| Standard_E4s_v3 | 4 | 32 | 64 | 8 | 8,000 / 64 (100) | 6,400 / 96 | 2 / moderate |
| Standard_E8s_v3 | 8 | 64 | 128 | 16 | 16,000 / 128 (200) | 12,800 / 192 | 4 / high |
| Standard_E16s_v3 | 16 | 128 | 256 | 32 | 32,000 / 256 (400) | 25,600 / 384 | 8 / high |
| Standard_E32s_v3 | 32 | 256 | 512 | 32 | 64,000 / 512 (800) | 51,200 / 768 | 8 / extremely high |
| Standard_E64s_v3 | 64 | 432 | 864 | 32 | 128,000/1024 (1600) | 80,000 / 1200 | 8 / extremely |
Geographic Availability
- US
- West 2
- East
- Europe
- West
- Asia Pacific
- Southeast
Microsoft will be rapidly adding the other regions and we will provide more updates as these regions become available.