The Memory and storage optimized Mdsv4 Medium Memory VM series are based on the 6th generation Intel® Xeon® Scalable processors and deliver higher remote disk storage performance. These new VM sizes offer up to 4 TB of RAM and up to 225,000 IOPS and 5.5 GBps throughput to remote disk storage with NVMe interface by using Ultra Disk and Premium SSD v2, and provides 50% networking performance improvements over previous generations.
Host specifications
| Part |
Quantity
Count Units |
Specs
SKU ID, Performance Units, etc. |
| Processor |
16 - 256 vCPUs |
Intel Xeon 6th gen Scalable (Granite Rapids) [x86-64] |
| Memory |
256 - 3892 GiB |
|
| Local Storage |
1 - 2 |
550 - 4400 GiB
125,000 - 2,000,000 IOPS
700 - 11,200 MBps |
| Remote Storage |
64 Disks |
20,000 - 225,000 IOPS
400 - 5,500 MBps |
| Network |
8 NICs |
4,500 - 50,000 Mbps
Interfaces: NetVSC, MANA |
| Accelerators |
None |
|
For features supported by this series, see the Feature support section.
Sizes in series (NVMe)
vCPUs (Qty.) and Memory for each size
| Size Name |
vCPUs (Qty.) |
Memory (GiB) |
| Standard_M16lds_v4 |
16 |
256 |
| Standard_M32lds_v4 |
32 |
512 |
| Standard_M48lds_v4 |
48 |
768 |
| Standard_M64lds_v4 |
64 |
1024 |
| Standard_M96lds_v4 |
96 |
1536 |
| Standard_M128lds_v4 |
128 |
1944 |
| Standard_M192lds_v4 |
192 |
3072 |
| Standard_M256lds_v4 |
256 |
3892 |
VM Basics resources
Local (temp) storage information for each size:
| Size Name |
Max Temp Storage Disks (Qty.) |
Temp Disk Size (GiB) |
Max Temp Disk Random Read (RR)1 IOPS |
Max Temp Disk Sequential Read Throughput (MBps) |
Temp Disk Random Write IOPS |
Temp Disk Sequential Write Throughput (MBps) |
| Standard_M16lds_v4 |
1 |
550 |
125,000 |
700 |
62,500 |
350 |
| Standard_M32lds_v4 |
1 |
1100 |
250,000 |
1,400 |
125,000 |
700 |
| Standard_M48lds_v4 |
1 |
1650 |
375,000 |
2,100 |
187,500 |
1,050 |
| Standard_M64lds_v4 |
2 |
1100 |
500,000 |
2,800 |
250,000 |
1,400 |
| Standard_M96lds_v4 |
2 |
1650 |
750,000 |
4,200 |
375,000 |
2,100 |
| Standard_M128lds_v4 |
2 |
2200 |
1,000,000 |
5,600 |
500,000 |
2,800 |
| Standard_M192lds_v4 |
2 |
3300 |
1,500,000 |
8,400 |
750,000 |
4,200 |
| Standard_M256lds_v4 |
2 |
4400 |
2,000,000 |
11,200 |
1,000,000 |
5,600 |
Table definitions
- Total local temporary storage is calculated by multiplying the max number of storage disks by the temp disk size. For example, for the Standard_M256lds_v4, the total local temporary storage capacity is 2 x 6000 GiB = 12000 GiB.
- Temp disk performance depends on many factors including block size, workload patterns of read/writes, queue depth (QD), and others. Temp disk performance specifications represent best case performance numbers, assuming 4k block sizes and QD=256 for IOPS, and 256k block sizes with QD=64 for throughput. Read performance specs assume 100% reads, and write performance specs assume 100% writes. Write performance is heavily impacted by how many blocks are in use on a device. Temp disk write performance specs assume a device has a clean slate to enable the best performance. During steady state operations, write performance is expected to be lower than the published specs.
- Storage capacity is shown in units of GiB or 1024^3 bytes. When you compare disks measured in GB (1000^3 bytes) to disks measured in GiB (1024^3), remember that capacity numbers given in GiB might 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.
- To learn how to get the best storage performance for your VMs, see Virtual machine and disk performance.
- NVMe temp disks are presented as raw NVMe devices that you need to initialize and format before use. For more details on how to format and initialize drives, refer to the NVMe Temp Disk FAQ.
Remote (uncached) storage information for each size:
| Size Name |
Max Remote Storage Disks (Qty.) |
Max Uncached Premium SSD IOPS |
Max Uncached Premium SSD Throughput (MB/s) |
Max Uncached Ultra Disk and Premium SSD v2 IOPS |
Max Uncached Ultra Disk and Premium SSD v2 Throughput (MB/s) |
| Standard_M16lds_v4 |
64 |
20,000 |
20,000 |
400 |
400 |
| Standard_M32lds_v4 |
64 |
40,000 |
40,000 |
800 |
800 |
| Standard_M48lds_v4 |
64 |
65,000 |
65,000 |
1,600 |
1,600 |
| Standard_M64lds_v4 |
64 |
80,000 |
80,000 |
1,600 |
1,600 |
| Standard_M96lds_v4 |
64 |
120,000 |
120,000 |
3,200 |
3,200 |
| Standard_M128lds_v4 |
64 |
160,000 |
160,000 |
4,000 |
4,000 |
| Standard_M192lds_v4 |
64 |
200,000 |
200,000 |
4,750 |
4,750 |
| Standard_M256lds_v4 |
64 |
225,000 |
225,000 |
5,500 |
5,500 |
Storage resources
Table definitions
- Storage capacity is shown in units of GiB or 1024^3 bytes. When you compare disks measured in GB (1000^3 bytes) to disks measured in GiB (1024^3), remember that capacity numbers given in GiB might 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.
- IOPS and MBps listed here refer to uncached mode for data disks.
- To learn how to get the best storage performance for your VMs, see Virtual machine and disk performance.
- The IOPS specification uses common small random block sizes like 4 KiB or 8 KiB. Maximum IOPS is defined as "up-to" and measured by using 4 KiB random reads workloads.
- The TPUT specification uses common large sequential block sizes like 128 KiB or 1024 KiB. Maximum TPUT is defined as "up-to" and measured by using 128 KiB sequential reads workloads.
Network interface information for each size:
| Size Name |
Max NICs (Qty.) |
Max Network Bandwidth (Mb/s) |
| Standard_M16lds_v4 |
8 |
4,500 |
| Standard_M32lds_v4 |
8 |
8,000 |
| Standard_M48lds_v4 |
8 |
16,000 |
| Standard_M64lds_v4 |
8 |
16,000 |
| Standard_M96lds_v4 |
8 |
30,000 |
| Standard_M128lds_v4 |
8 |
30,000 |
| Standard_M192lds_v4 |
8 |
50,000 |
| Standard_M256lds_v4 |
8 |
50,000 |
Networking resources
Table definitions
- Expected network bandwidth is the maximum aggregated bandwidth allocated per VM type across all NICs, for all destinations. For more information, see Virtual machine network bandwidth.
- Upper limits aren't guaranteed. Limits offer guidance for selecting the right VM type for the intended application. Actual network performance depends on several factors including network congestion, application loads, and network settings. For information on optimizing network throughput, see Optimize network throughput for Azure virtual machines.
- To achieve the expected network performance on Linux or Windows, you might need to select a specific version or optimize your VM. For more information, see Bandwidth/Throughput testing (NTTTCP).
Accelerator (GPUs, FPGAs, etc.) info for each size
Note
This series doesn't include any accelerators.
Feature support
List of all available sizes: Sizes
Pricing Calculator: Pricing Calculator
Information on Disk Types: Disk Types
Next steps
Take advantage of the latest performance and features available for your workloads by changing the size of a virtual machine.
Utilize Microsoft's in-house designed ARM processors with Azure Cobalt VMs.
Learn how to Monitor Azure virtual machines.