The Lsv4-series of Azure Virtual Machines (VMs) features high-throughput, low latency, directly mapped local NVMe storage. These VMs utilize the fifth Generation Intel® Xeon® Platinum 8573C (Emerald Rapids) processor reaching an all- core turbo clock speed of 3.0 GHz. The Lsv4-series VMs are available in sizes from 2 to 96 vCPUs, with 8 GiB of memory allocated per vCPU and 240GB of local NVMe temp disk capacity allocated per vCPU, with up to 23TB (12x1.92TB) of local temp disk capacity available on the L96s_v4 size.
Lsv4-series VMs are well suited for scale-up or scale-out storage workloads that need a balance of SSD capacity, compute, and memory. These VMs are perfect for big data, relational, NoSQL databases, data analytics, and data warehousing workloads. Examples include Cassandra, MongoDB, Cloudera, Spark, Elastic Search, Redis, and other data-intensive applications.
Lsv4-series VMs support Standard SSD, Standard HDD, and Premium SSD remote disk types. You can also attach Ultra Disk storage based on its regional availability. Remote Disk storage is billed separately from virtual machines.
Host specifications
| Part |
Quantity
Count Units |
Specs
SKU ID, Performance Units, etc. |
| Processor |
2 - 96 vCPUs |
Intel Xeon Platinum 8573C (Emerald Rapids) [x86-64] |
| Memory |
16 - 768 GiB |
|
| Local Storage |
1 - 12 Disk |
480 - 1920 GB
137500 - 6600000 IOPS
750 - 36000 MBps |
| Remote Storage |
8 - 64 Disks |
3,750 - 153,600 IOPS
106 - 5,088 MBps |
| Network |
2 - 8 NICs |
12,500 - 41,000 Mbps |
| Accelerators |
None |
|
Feature support
Premium Storage: Supported
Premium Storage caching: Supported (except for L96s_v4)
Live Migration: Not Supported
Memory Preserving Updates: Supported
Generation 2 VMs: Supported
Generation 1 VMs: Not Supported
Accelerated Networking: Supported
Ephemeral OS Disk: Supported
Nested Virtualization: Supported
Sizes in series
vCPUs (Qty.) and Memory for each size.
| Size Name |
vCPUs (Qty.) |
Memory (GiB) |
| Standard_L2s_v4 |
2 |
16 |
| Standard_L4s_v4 |
4 |
32 |
| Standard_L8s_v4 |
8 |
64 |
| Standard_L16s_v4 |
16 |
128 |
| Standard_L32s_v4 |
32 |
256 |
| Standard_L48s_v4 |
48 |
384 |
| Standard_L64s_v4 |
64 |
512 |
| Standard_L80s_v4 |
80 |
640 |
| Standard_L96s_v4 |
96 |
768 |
VM Basics resources
Local (temp) storage info for each size.
| Size Name |
Max Temp Storage Disks (Qty.) |
Temp Disk Size (GB) |
Temp Disk Random Read1 IOPS |
Temp Disk Sequential Read1 Throughput (MB/s) |
Temp Disk Random Write1 IOPS |
Temp Disk Sequential Write1 Throughput (MB/s) |
| Standard_L2s_v4 |
1 |
480 |
137500 |
750 |
55000 |
375 |
| Standard_L4s_v4 |
2 |
480 |
275000 |
1500 |
110000 |
750 |
| Standard_L8s_v4 |
4 |
480 |
550000 |
3000 |
220000 |
1500 |
| Standard_L16s_v4 |
4 |
960 |
1100000 |
6000 |
440000 |
3000 |
| Standard_L32s_v4 |
8 |
960 |
2200000 |
12000 |
880000 |
6000 |
| Standard_L48s_v4 |
6 |
1920 |
3300000 |
18000 |
1320000 |
9000 |
| Standard_L64s_v4 |
8 |
1920 |
4400000 |
24000 |
1760000 |
12000 |
| Standard_L80s_v4 |
10 |
1920 |
5500000 |
30000 |
2200000 |
15000 |
| Standard_L96s_v4 |
12 |
1920 |
6600000 |
36000 |
2640000 |
18000 |
Storage resources
Table definitions
- 1Temp disk performance depends on many factors including block size, workload patterns of read/writes, queue depth (QD), and others. Temp disk performance specifications should be viewed as best case performance numbers, assuming 4k block sizes and QD=256 for IOPS, and 256k block sizes with QD=64 for throughput. Additionally, write performance is heavily impacted by how many blocks 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.
- For Lsv4, temp disk refers to the NVMe local data disks used by the VM. While Lsv3/Lasv3 have NVMe local data disks and a SCSI local temp disk, Lsv4 only has NVMe local temp disks. There is no SCSI local temp disk on Lsv4.
- 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 local storage performance for your VMs, see the NVMe Temp Disk FAQ.
Remote (uncached) storage info for each size.
| Size Name |
Max Remote Storage Disks (Qty.) |
Uncached Premium SSD Disk IOPS |
Uncached Premium SSD Throughput (MB/s) |
Uncached Premium SSD Burst1 IOPS |
Uncached Premium SSD Burst1 Throughput (MB/s) |
Uncached Ultra Disk and Premium SSD v2 IOPS |
Uncached Ultra Disk and Premium SSD v2 Throughput (MB/s) |
Uncached Burst1 Ultra Disk and Premium SSD v2 IOPS |
Uncached Burst1 Ultra Disk and Premium SSD v2 Disk Throughput (MB/s) |
| Standard_L2s_v4 |
8 |
3,750 |
106 |
40,000 |
1,250 |
4,157 |
124 |
44,444 |
1,463 |
| Standard_L4s_v4 |
12 |
6,400 |
212 |
40,000 |
1,250 |
8,333 |
248 |
52,083 |
1,463 |
| Standard_L8s_v4 |
24 |
12,800 |
424 |
40,000 |
1,250 |
16,667 |
496 |
52,083 |
1,463 |
| Standard_L16s_v4 |
48 |
25,600 |
848 |
40,000 |
1,250 |
33,333 |
992 |
52,083 |
1,463 |
| Standard_L32s_v4 |
64 |
51,200 |
1,696 |
80,000 |
1,696 |
66,667 |
1,984 |
104,167 |
1,984 |
| Standard_L48s_v4 |
64 |
76,800 |
2,544 |
80,000 |
2,544 |
100,000 |
2,976 |
104,167 |
2,976 |
| Standard_L64s_v4 |
64 |
102,400 |
3,392 |
102,400 |
3,392 |
133,333 |
3,969 |
133,333 |
3,969 |
| Standard_L80s_v4 |
64 |
128,000 |
4,240 |
128,000 |
4,240 |
166,640 |
4,960 |
166,640 |
4,960 |
| Standard_L96s_v4 |
64 |
153,600 |
5,088 |
153,600 |
5,088 |
200,000 |
5,953 |
200,000 |
5,953 |
Storage resources
Table definitions
- 1Some sizes support bursting to temporarily increase disk performance. Burst speeds can be maintained for up to 30 minutes at a time.
- 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 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.
- To learn how to get the best storage performance for your VMs, see Virtual machine and disk performance.
Network interface info for each size.
| Size Name |
Max NICs (Qty.) |
Max Network Bandwidth (Mb/s) |
| Standard_L2s_v4 |
2 |
12,500 |
| Standard_L4s_v4 |
2 |
12,500 |
| Standard_L8s_v4 |
4 |
12,500 |
| Standard_L16s_v4 |
8 |
12,500 |
| Standard_L32s_v4 |
8 |
16,000 |
| Standard_L48s_v4 |
8 |
24,000 |
| Standard_L64s_v4 |
8 |
30,000 |
| Standard_L80s_v4 |
8 |
36,000 |
| Standard_L96s_v4 |
8 |
41,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 will depend 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 may 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
No accelerators are present in this series.
Note
This VM series will only work on OS images that support NVMe. If your current OS image doesn't have NVMe support, you’ll see an error message. NVMe support is available on the most popular OS images, and we're continuously improving OS image compatibility.
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.