D-Series VM’s for Microsoft Azure, read more….
I’ve been getting some questions from customers about the D-Series VMs so that I would report this info.
D-Series VM’s provide great performance for applications needing fast, local (ephemeral) storage or a faster CPU; however, it’s important to understand a little about how the system is configured to ensure you’re getting an optimal experience.
For the new D-Series, here are the core counts and RAM assignment, as well as the capacity and performance expectations for local SSD by VM type:
| Name | Cores | Memory (GB) | Local SSD Size (GB) | Local SSD Max IOPS | Local SSD Max Read MB/s | Local SSD Max Write MB/s |
| Standard_D1 | 1 | 3.5 | 50 | 3,000 | 48 | 24 |
| Standard_D2 | 2 | 7 | 100 | 6,000 | 96 | 48 |
| Standard_D3 | 4 | 14 | 200 | 12,000 | 192 | 96 |
| Standard_D4 | 8 | 28 | 400 | 24,000 | 384 | 192 |
| Standard_D11 | 2 | 14 | 100 | 6,000 | 96 | 48 |
| Standard_D12 | 4 | 28 | 200 | 12,000 | 192 | 96 |
| Standard_D13 | 8 | 56 | 400 | 24,000 | 384 | 192 |
| Standard_D14 | 16 | 112 | 800 | 48,000 | 768 | 384 |
IO Operations are limited by either Max IOPs or the Max Read/Write throughput (MB/s), whichever they hit first (for mixed workloads a write effectively counts double against the read limit). Small IO sizes will typically max out on IOPS before hitting bandwidth limits, while large IO sizes will typically max out on bandwidth before hitting IOPS limits.
Here’s the pricing for all VM’s -
More Microsoft Azure training please go to the Microsoft Virtual Academy at https://aka.ms/go-mva