Add Dv2 VM size info · MicrosoftDocs/azure-docs@c68b700 (original) (raw)
`@@ -31,7 +31,9 @@ Azure Virtual Machines and Cloud Services are two of several types of compute re
`
31
31
``
32
32
`Virtual machines are available in two tiers: basic and standard. Both types offer a choice of sizes, but the basic tier doesn’t provide some capabilities available in the standard tier, such as load-balancing and auto-scaling. The standard tier of sizes consists of different series: A, D, DS, G, and GS. Considerations for some of these sizes include:
`
33
33
``
34
``
`-
- 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.
`
``
34
`+
- 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.
`
``
35
+
``
36
`+
- 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.2 GHz. The Dv2-Series has the same memory and disk configurations as the D-series. For details, see the announcement on the Azure blog, New Dv2-Series Virtual Machine Sizes.
`
35
37
``
36
38
`* G-series VMs offer the biggest size and best performance and run on hosts that have Intel Xeon E5 V3 family processors.
`
37
39
``
`@@ -49,7 +51,9 @@ The following considerations might help you decide on a size:
`
49
51
``
50
52
`* 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 the topic Error: “Failed to configure virtual machine” on the support forum for workarounds for each deployment scenario.
`
51
53
``
52
``
`-
- The A8/A10 and A9/A11 virtual machine sizes have the same capacities. The A8 and A9 virtual machine instances include an additional network adapter that is connected to a remote direct memory access (RDMA) network for fast communication between virtual machines. The A8 and A9 instances are designed for high-performance computing applications that require constant and low-latency communication between nodes during execution, for example, applications that use the Message Passing Interface (MPI). The A10 and A11 virtual machine instances do not include the additional network adapter. A10 and A11 instances are designed for high-performance computing applications that do not require constant and low-latency communication between nodes, also known as parametric or embarrassingly parallel applications.
`
``
54
`+
- The A8/A10 and A9/A11 virtual machine sizes have the same capacities. The A8 and A9 virtual machine instances include an additional network adapter that is connected to a remote direct memory access (RDMA) network for fast communication between virtual machines. The A8 and A9 instances are designed for high-performance computing applications that require constant and low-latency communication between nodes during execution, for example, applications that use the Message Passing Interface (MPI). The A10 and A11 virtual machine instances do not include the additional network adapter. A10 and A11 instances are designed for high-performance computing applications that do not require constant and low-latency communication between nodes, also known as parametric or embarrassingly parallel applications.
`
``
55
+
``
56
`+
- Dv2-Series and D-Series 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.
`
53
57
``
54
58
`## General limits
`
55
59
``
`@@ -77,8 +81,7 @@ The following tables show the sizes and the capacities they provide.
`
77
81
`|A3\Basic_A3|4|7 GB|
OS = 1023 GB
Temporary = 120 GB
|8|8x300|`
78
82
`|A4\Basic_A4|8|14 GB|
OS = 1023 GB
Temporary = 240 GB
|16|16x300|`
79
83
``
80
``
`-
Standard tier
`
81
``
`-
A series and D series
`
``
84
`+
Standard tier - A series
`
82
85
``
83
86
`|Size – Azure Portal\cmdlets & APIs|CPU cores|Memory|Max. disk sizes – virtual machine|Max. data disks (1023 GB each)|Max. IOPS (500 per disk)|
`
84
87
`|---|---|---|---|---|---|
`
`@@ -94,6 +97,11 @@ The following tables show the sizes and the capacities they provide.
`
94
97
`|A9\same|16|112 GB|
OS = 1023 GB
Temporary = 382 GB
|16|16x500|Note: For information and considerations about using this size, see About the A8, A9, A10, and A11 compute intensive instances.
`
95
98
`|A10\same|8|56 GB|
OS = 1023 GB
Temporary = 382 GB
|16|16x500|Note: For information and considerations about using this size, see About the A8, A9, A10, and A11 compute intensive instances.
`
96
99
`|A11\same|16|112 GB|
OS = 1023 GB
Temporary = 382 GB
|16|16x500|Note: For information and considerations about using this size, see About the A8, A9, A10, and A11 compute intensive instances.
`
``
100
+
``
101
`+
Standard tier – D series
`
``
102
+
``
103
`+
|Size – Azure Portal\cmdlets & APIs|CPU cores|Memory|Max. disk sizes – virtual machine|Max. data disks (1023 GB each)|Max. IOPS (500 per disk)|
`
``
104
`+
|---|---|---|---|---|---|
`
97
105
`|Standard_D1\same|1|3.5 GB|
OS = 1023 GB
Temporary (SSD) =50 GB
|2|2x500|`
98
106
`|Standard_D2\same|2|7 GB|
OS = 1023 GB
Temporary (SSD) =100 GB
|4|4x500|`
99
107
`|Standard_D3\same|4|14 GB|
OS = 1023 GB
Temporary (SSD) =200 GB
|8|8x500|`
`@@ -103,6 +111,19 @@ The following tables show the sizes and the capacities they provide.
`
103
111
`|Standard_D13\same|8|56 GB|
OS = 1023 GB
Temporary (SSD) =400 GB
|16|16x500|`
104
112
`|Standard_D14\same|16|112 GB|
OS = 1023 GB
Temporary (SSD) =800 GB
|32|32x500|`
105
113
``
``
114
`+
Standard tier – Dv2 series
`
``
115
+
``
116
`+
|Size – Azure Portal\cmdlets & APIs|CPU cores|Memory|Max. disk sizes – virtual machine|Max. data disks (1023 GB each)|Max. IOPS (500 per disk)|
`
``
117
`+
|---|---|---|---|---|---|
`
``
118
`+
|Standard_D1_v2\same|1|3.5 GB|
OS = 1023 GB
Temporary (SSD) =50 GB
|2|2x500|`
``
119
`+
|Standard_D2_v2\same|2|7 GB|
OS = 1023 GB
Temporary (SSD) =100 GB
|4|4x500|`
``
120
`+
|Standard_D3_v2\same|4|14 GB|
OS = 1023 GB
Temporary (SSD) =200 GB
|8|8x500|`
``
121
`+
|Standard_D4_v2\same|8|28 GB|
OS = 1023 GB
Temporary (SSD) =400 GB
|16|16x500|`
``
122
`+
|Standard_D5_v2\same|16|56 GB|
OS = 1023 GB
Temporary (SSD) =800 GB
|32|32x500|`
``
123
`+
|Standard_D11_v2\same|2|14 GB|
OS = 1023 GB
Temporary (SSD) =100 GB
|4|4x500|`
``
124
`+
|Standard_D12_v2\same|4|28 GB|
OS = 1023 GB
Temporary (SSD) =200 GB
|8|8x500|`
``
125
`+
|Standard_D13_v2\same|8|56 GB|
OS = 1023 GB
Temporary (SSD) =400 GB
|16|16x500|`
``
126
`+
|Standard_D14_v2\same|16|112 GB|
OS = 1023 GB
Temporary (SSD) =800 GB
|32|32x500|`
106
127
``
107
128
`### Standard tier – DS series*
`
108
129
``