Storage optimized

The Ls-series is optimized for workloads that require low latency temporary storage, like NoSQL databases including Cassandra, MongoDB, Cloudera, and Redis. The Ls-series offers up to 32 vCPUs, using the Intel® Xeon® processor E5 v3 family. The Ls-series gets the same CPU performance as the G/GS-Series and comes with 8 GiB of memory per vCPU.


ACU: 180-240

Size vCPU Memory: GiB Temp storage (SSD) GiB Max data disks Max cached and temp storage throughput: IOPS / MBps (cache size in GiB) Max uncached disk throughput: IOPS / MBps Max NICs / Expected network performance (Mbps)
Standard_L4s 4 32 678 8 NA / NA (0) 5,000 / 125 2 / 4000
Standard_L8s 8 64 1,388 16 NA / NA (0) 10,000 / 250 4 / 8000
Standard_L16s 16 128 2,807 32 NA / NA (0) 20,000 / 500 8 / 6000 - 16000 †
Standard_L32s* 32 256 5,630 64 NA / NA (0) 40,000 / 1,000 8 / 20000

The maximum disk throughput possible with Ls-series VMs may be limited by the number, size, and striping of any attached disks. For details, see Premium Storage: High-performance storage for Azure virtual machine workloads.

*Instance is isolated to hardware dedicated to a single customer.

Size table definitions

  • Storage capacity is shown in units of GiB or 1024^3 bytes. When comparing 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.
  • Expected network performance is the maximum aggregated bandwidth allocated per VM type across all NICs, for all destinations. Upper limits are not guaranteed, but are intended to provide guidance for selecting the right VM type for the intended application. Actual network performance will depend on a variety of factors including network congestion, application loads, and network settings. For information on optimizing network throughput, see Optimizing network throughput for Windows and Linux. To achieve the expected network performance on Linux or Windows, it may be necessary to select a specific version or optimize your VM. For more information, see How to reliably test for virtual machine throughput.

  • † 16 vCPU performance will consistently reach the upper limit in an upcoming release.

Other sizes

Next steps

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