Compute optimized virtual machine sizes

This article lists the different compute optimized sizes available for Windows virtual machines (VM) in Azure.

Compute optimized VM sizes have a high CPU-to-memory ratio. These sizes are good for medium traffic web servers, network appliances, batch processes, and application servers. This article provides information about the number of vCPUs, data disks, and NICs. It also includes information about storage throughput and network bandwidth for each size in this grouping.

The Fsv2-series is based on the Intel® Xeon® Platinum 8168 processor. It features a sustained all core Turbo clock speed of 3.4 GHz and a maximum single-core turbo frequency of 3.7 GHz. Intel® AVX-512 instructions are new on Intel Scalable Processors. These instructions provide up to a 2X performance boost to vector processing workloads on both single and double precision floating point operations. In other words, they're really fast for any computational workload.

At a lower per-hour list price, the Fsv2-series is the best value in price-performance in the Azure portfolio based on the Azure Compute Unit (ACU) per vCPU.

Fsv2-series 1

ACU: 195 - 210

Premium Storage: Supported

Premium Storage caching: Supported

Size vCPUs 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 bandwidth (Mbps)
Standard_F2s_v2 2 4 16 4 4000 / 31 (32) 3200 / 47 2 / 875
Standard_F4s_v2 4 8 32 8 8000 / 63 (64) 6400 / 95 2 / 1750
Standard_F8s_v2 8 16 64 16 16000 / 127 (128) 12800 / 190 4 / 3500
Standard_F16s_v2 16 32 128 32 32000 / 255 (256) 25600 / 380 4 / 7000
Standard_F32s_v2 32 64 256 32 64000 / 512 (512) 51200 / 750 8 / 14000
Standard_F48s_v2 48 96 384 32 96000 / 768 (768) 76800 / 1100 8 / 21000
Standard_F64s_v2 64 128 512 32 128000 / 1024 (1024) 80000 / 1100 8 / 28000
Standard_F72s_v22, 3 72 144 576 32 144000 / 1152 (1520) 80000 / 1100 8 / 30000

1 Fsv2-series VMs feature Intel® Hyper-Threading Technology.

2 The use of more than 64 vCPU require one of these supported guest operating systems: Windows Server 2016, Ubuntu 16.04 LTS, SLES 12 SP2, and Red Hat Enterprise Linux, CentOS 7.3, or Oracle Linux 7.3 with LIS 4.2.1.

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

  • If you want to get the best performance for your VMs, you should limit the number of data disks to two disks per vCPU.

  • 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

Next steps

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