Skip to content

Latest commit

 

History

History
208 lines (183 loc) · 10.3 KB

constrained-vcpu.md

File metadata and controls

208 lines (183 loc) · 10.3 KB
title description author ms.service ms.subservice ms.topic ms.date ms.author ms.reviewer
Constrained vCPU sizes
Lists the Vm sizes that are capable of having a constrained vCPU count. Useful for per-core licensed database workloads.
mattmcinnes
azure-virtual-machines
sizes
conceptual
03/11/2025
mattmcinnes
mimckitt

Constrained vCPU sizes for database workloads

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

Tip

Try the Virtual Machine selector tool to find other sizes that best fit your workload.

Some database workloads require high memory, storage, and I/O bandwidth, but don't benefit from a high number of cores. Products designed for these workloads are often licensed on a per-CPU-core basis. This licensing system means that a VM size with otherwise ideal specifications but an excessive vCPU count can cause a substantial increase in licensing costs. To help manage your costs, Azure offers predefined VM sizes with a lowered vCPU count to help to reduce the cost of software licensing, while maintaining the same memory, storage, and I/O bandwidth.

The original size's available vCPU count can be reduced to either one half or one quarter of the original size specification. These new VM sizes have a suffix that specifies the number of available vCPUs to make them easier for you to identify. Learn more about VM size naming conventions.

Example workload

The licensing fees charged for SQL Server are based on the available vCPU count. Third party products should count the available vCPUs and report it as the amount to be used and licensed. This constraint results in a 50% to 75% increase in the ratio of the VM specs to available (billable) vCPUs while maintaining the benefits of the original VM size's specifications.

Specification comparison

The Standard_E32s_v5 VM size comes with 32 vCPUs, 256 GiB of RAM, 32 disks, and 80,000 IOPs of I/O bandwidth. The pre-defined Standard_E32-16s_v5 and Standard_E32-8s_v5 VM sizes comes with 16 and 8 active vCPUs respectively, while maintaining the memory, storage, and I/O bandwidth specifications of the Standard_E32s_v5.

Size type Size name Disabled vCPUs Active vCPUs Memory, Storage, I/O
Base (Original) Standard_E32s_v5 0 32 256 GiB, 32 Disks, 80,000 IOPs
Constrained Standard_E32-16s_v5 16 16 256 GiB, 32 Disks, 80,000 IOPs
Constrained Standard_E32-8s_v5 24 8 256 GiB, 32 Disks, 80,000 IOPs

Note

Disabled vCPUs are not available for use by the VM. If your VM has multiple workloads assigned to it then it may require more vCPUs. If possible, relocate secondary tasks to another virtual machine to avoid increased licensing costs.

Pricing

At this time, the VM pricing, remains the same as the original size. For more information, see Azure VM sizes for more cost-effective database workloads.

List of available sizes with constrained vCPUs

Size name Active vCPUs Base size
Standard_M8-2ms 2 M8ms
Standard_M8-4ms 4 M8ms
Standard_M16-4ms 4 M16ms
Standard_M16-8ms 8 M16ms
Standard_M32-8ms 8 M32ms
Standard_M32-16ms 16 M32ms
Standard_M64-32ms 32 M64ms
Standard_M64-16ms 16 M64ms
Standard_M128-64ms 64 M128ms
Standard_M128-32ms 32 M128ms
Standard_M416-208s_v2 208 M416s_v2
Standard_M416-208ms_v2 208 M416ms_v2
Size name Active vCPUs Base size
Standard_E4-2s_v3 2 E4s_v3
Standard_E8-4s_v3 4 E8s_v3
Standard_E8-2s_v3 2 E8s_v3
Standard_E16-8s_v3 8 E16s_v3
Standard_E16-4s_v3 4 E16s_v3
Standard_E32-16s_v3 16 E32s_v3
Standard_E32-8s_v3 8 E32s_v3
Standard_E64-32s_v3 32 E64s_v3
Standard_E64-16s_v3 16 E64s_v3
Standard_E4-2s_v4 2 E4s_v4
Standard_E8-4s_v4 4 E8s_v4
Standard_E8-2s_v4 2 E8s_v4
Standard_E16-8s_v4 8 E16s_v4
Standard_E16-4s_v4 4 E16s_v4
Standard_E32-16s_v4 16 E32s_v4
Standard_E32-8s_v4 8 E32s_v4
Standard_E64-32s_v4 32 E64s_v4
Standard_E64-16s_v4 16 E64s_v4
Standard_E4-2ds_v4 2 E4ds_v4
Standard_E8-4ds_v4 4 E8ds_v4
Standard_E8-2ds_v4 2 E8ds_v4
Standard_E16-8ds_v4 8 E16ds_v4
Standard_E16-4ds_v4 4 E16ds_v4
Standard_E32-16ds_v4 16 E32ds_v4
Standard_E32-8ds_v4 8 E32ds_v4
Standard_E64-32ds_v4 32 E64ds_v4
Standard_E64-16ds_v4 16 E64ds_v4
Standard_E4-2s_v5 2 E4s_v5
Standard_E8-4s_v5 4 E8s_v5
Standard_E8-2s_v5 2 E8s_v5
Standard_E16-8s_v5 8 E16s_v5
Standard_E16-4s_v5 4 E16s_v5
Standard_E32-16s_v5 16 E32s_v5
Standard_E32-8s_v5 8 E32s_v5
Standard_E64-32s_v5 32 E64s_v5
Standard_E64-16s_v5 16 E64s_v5
Standard_E96-48s_v5 48 E96s_v5
Standard_E96-24s_v5 24 E96s_v5
Standard_E4-2ds_v5 2 E4ds_v5
Standard_E8-4ds_v5 4 E8ds_v5
Standard_E8-2ds_v5 2 E8ds_v5
Standard_E16-8ds_v5 8 E16ds_v5
Standard_E16-4ds_v5 4 E16ds_v5
Standard_E32-16ds_v5 16 E32ds_v5
Standard_E32-8ds_v5 8 E32ds_v5
Standard_E64-32ds_v5 32 E64ds_v5
Standard_E64-16ds_v5 16 E64ds_v5
Standard_E96-48ds_v5 48 E96ds_v5
Standard_E96-24ds_v5 24 E96ds_v5
Standard_E4-2as_v4 2 E4as_v4
Standard_E8-4as_v4 4 E8as_v4
Standard_E8-2as_v4 2 E8as_v4
Standard_E16-8as_v4 8 E16as_v4
Standard_E16-4as_v4 4 E16as_v4
Standard_E32-16as_v4 16 E32as_v4
Standard_E32-8as_v4 8 E32as_v4
Standard_E64-32as_v4 32 E64as_v4
Standard_E64-16as_v4 16 E64as_v4
Standard_E96-48as_v4 48 E96as_v4
Standard_E96-24as_v4 24 E96as_v4
Standard_E4-2ads_v5 2 E4ads_v5
Standard_E8-4ads_v5 4 E8ads_v5
Standard_E8-2ads_v5 2 E8ads_v5
Standard_E16-8ads_v5 8 E16ads_v5
Standard_E16-4ads_v5 4 E16ads_v5
Standard_E32-16ads_v5 16 E32ads_v5
Standard_E32-8ads_v5 8 E32ads_v5
Standard_E64-32ads_v5 32 E64ads_v5
Standard_E64-16ads_v5 16 E64ads_v5
Standard_E96-48ads_v5 48 E96ads_v5
Standard_E96-24ads_v5 24 E96ads_v5
Standard_E4-2as_v5 2 E4as_v5
Standard_E8-4as_v5 4 E8as_v5
Standard_E8-2as_v5 2 E8as_v5
Standard_E16-8as_v5 8 E16as_v5
Standard_E16-4as_v5 4 E16as_v5
Standard_E32-16as_v5 16 E32as_v5
Standard_E32-8as_v5 8 E32as_v5
Standard_E64-32as_v5 32 E64as_v5
Standard_E64-16as_v5 16 E64as_v5
Standard_E96-48as_v5 48 E96as_v5
Standard_E96-24as_v5 24 E96as_v5
Standard_E4-2s_v6 4 E4s_v6
Standard_E8-2s_v6 8 E8s_v6
Standard_E8-4s_v6 8 E8s_v6
Standard_E16-4s_v6 16 E16s_v6
Standard_E16-8s_v6 16 E16s_v6
Standard_E32-8s_v6 32 E32s_v6
Standard_E32-16s_v6 32 E32s_v6
Standard_E64-16s_v6 64 E64s_v6
Standard_E64-32s_v6 64 E64s_v6
Standard_E96-24s_v6 96 E96s_v6
Standard_E96-48s_v6 96 E96s_v6
Standard_E128-32s_v6 128 E128s_v6
Standard_E128-64s_v6 128 E128s_v6
Standard_E4-2ds_v6 4 4 E4ds_v6
Standard_E8-2ds_v6 8 E8ds_v6
Standard_E8-4ds_v6 8 E8ds_v6
Standard_E16-4ds_v6 16 E16ds_v6
Standard_E16-8ds_v6 16 E16ds_v6
Standard_E32-8ds_v6 32 E32ds_v6
Standard_E32-16ds_v6 32 E32ds_v6
Standard_E64-16ds_v6 64 E64ds_v6
Standard_E64-32ds_v6 64 E64ds_v6
Standard_E96-24ds_v6 96 E96ds_v6
Standard_E96-48ds_v6 96 E96ds_v6
Standard_E128-32ds_v6 128 E128ds_v6
Standard_E128-64ds_v6 128 E128ds_v6
Size name Active vCPUs Base size
Standard_GS4-8 8 GS4
Standard_GS4-4 4 GS4
Standard_GS5-16 16 GS5
Standard_GS5-8 8 GS5
Size name Active vCPUs Base size
Standard_DS11-1_v2 1 DS11_v2
Standard_DS12-2_v2 2 DS12_v2
Standard_DS12-1_v2 1 DS12_v2
Standard_DS13-4_v2 4 DS13_v2
Standard_DS13-2_v2 2 DS13_v2
Standard_DS14-8_v2 8 DS14_v2
Standard_DS14-4_v2 4 DS14_v2

Other standard sizes

Next steps

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