Lsv3-series

Applies to: ✔️ Linux VMs ✔️ Windows VMs ✔️ Flexible scale sets ✔️ Uniform scale sets

The Lsv3-series of Azure Virtual Machines (Azure VMs) features high-throughput, low latency, directly mapped local NVMe storage. These VMs run on the 3rd Generation Intel® Xeon® Platinum 8370C (Ice Lake) processor in a hyper-threaded configuration. This new processor features an all-core turbo clock speed of 3.5 GHz with Intel® Turbo Boost Technology, Intel® Advanced-Vector Extensions 512 (Intel® AVX-512) and Intel® Deep Learning Boost.

The Lsv3-series VMs are available in sizes from 8 to 80 vCPUs. There are 8 GiB of memory allocated per vCPU, and one 1.92TB NVMe SSD device allocated per 8 vCPUs, with up to 19.2TB (10x1.92TB) available on the L80s_v3 size.

Note

The Lsv3-series VMs are optimized to use the local disk on the node attached directly to the VM rather than using durable data disks. This method allows for greater IOPS and throughput for your workloads. The Lsv3, Lasv3, Lsv2, and Ls-series VMs don't support the creation of a host cache to increase the IOPS achievable by durable data disks.

The high throughput and IOPS of the local disk makes the Lsv3-series VMs ideal for NoSQL stores such as Apache Cassandra and MongoDB. These stores replicate data across multiple VMs to achieve persistence in the event of the failure of a single VM.

To learn more, see how to optimize performance on the Lsv3-series Windows-based VMs or Linux-based VMs.

Size vCPU Memory (GiB) Temp disk (GiB) NVMe Disks NVMe Disk throughput (Read IOPS/MBps) Uncached data disk throughput (IOPS/MBps) Max burst uncached data disk throughput (IOPS/MBps) Max Data Disks Max NICs Expected network bandwidth (Mbps)
Standard_L8s_v3 8 64 80 1x1.92 TB 400000/2000 12800/290 20000/1200 16 4 12500
Standard_L16s_v3 16 128 160 2x1.92 TB 800000/4000 25600/600 40000/1600 32 8 12500
Standard_L32s_v3 32 256 320 4x1.92 TB 1.5M/8000 51200/865 80000/2000 32 8 16000
Standard_L48s_v3 48 384 480 6x1.92 TB 2.2M/14000 76800/1315 80000/3000 32 8 24000
Standard_L64s_v3 64 512 640 8x1.92 TB 2.9M/16000 80000/1735 80000/3000 32 8 30000
Standard_L80s_v3 80 640 800 10x1.92TB 3.8M/20000 80000/2160 80000/3000 32 8 32000
  1. Temp disk: Lsv3-series VMs have a standard SCSI-based temp resource disk for use by the OS paging or swap file (D: on Windows, /dev/sdb on Linux). This disk provides 80 GiB of storage, 4,000 IOPS, and 80 MBps transfer rate for every 8 vCPUs. For example, Standard_L80s_v3 provides 800 GiB at 40000 IOPS and 800 MBPS. This configuration ensures the NVMe drives can be fully dedicated to application use. This disk is ephemeral, and all data is lost on stop or deallocation.
  2. NVMe Disks: NVMe disk throughput can go higher than the specified numbers. However, higher performance isn't guaranteed. Local NVMe disks are ephemeral. Data is lost on these disks if you stop or deallocate your VM. Local NVMe disks aren't encrypted by Azure Storage encryption, even if you enable encryption at host.
  3. NVMe Disk throughput: Hyper-V NVMe Direct technology provides unthrottled access to local NVMe drives mapped securely into the guest VM space. Lsv3 NVMe disk throughput can go higher than the specified numbers, but higher performance isn't guaranteed. To achieve maximum performance, see how to optimize performance on the Lsv3-series Windows-based VMs or Linux-based VMs. Read/write performance varies based on IO size, drive load, and capacity utilization.
  4. Max burst uncached data disk throughput: Lsv3-series VMs can burst their disk performance for up to 30 minutes at a time.

Note

Lsv3-series VMs don't provide host cache for data disk as it doesn't benefit the Lsv3 workloads.

Size 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 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.

  • 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).

Other sizes and information

Pricing Calculator: Pricing Calculator

More information on Disks Types: Disk Types

Next steps

Learn more about how Azure compute units (ACU) can help you compare compute performance across Azure SKUs.