支持受约束 vCPU 的 VM 大小Constrained vCPU capable VM sizes

某些数据库工作负荷(如 SQL Server 或 Oracle)需要高内存、存储和 I/O 带宽,但不需要高核心计数。Some database workloads like SQL Server or Oracle require high memory, storage, and I/O bandwidth, but not a high core count. 许多数据库工作负荷不是 CPU 密集型工作负荷。Many database workloads are not CPU-intensive. Azure 提供了某些 VM 大小(其中你可以限制 VM vCPU 计数),以降低软件许可成本,同时保持相同的内存、存储和 I/O 带宽。Azure offers certain VM sizes where you can constrain the VM vCPU count to reduce the cost of software licensing, while maintaining the same memory, storage, and I/O bandwidth.

可将 vCPU 计数限制为一半或四分之一的原始 VM 大小。The vCPU count can be constrained to one half or one quarter of the original VM size. 这些新 VM 大小具有可指定活动的 vCPU 数的后缀,以便可以更轻松地识别。These new VM sizes have a suffix that specifies the number of active vCPUs to make them easier for you to identify.

为 SQL Server 或 Oracle 收取的许可费受限于新的 vCPU 计数,对其他产品应基于新的 vCPU 计数收取费用。The licensing fees charged for SQL Server or Oracle are constrained to the new vCPU count, and other products should be charged based on the new vCPU count. 这会导致 VM 规格与活动(可计费)vCPU 数的比率增加 50% 到 75%。This results in a 50% to 75% increase in the ratio of the VM specs to active (billable) vCPUs. 这些新的 VM 大小允许客户工作负荷使用相同的内存、存储和 I/O 带宽,同时优化其软件许可成本。These new VM sizes allow customer workloads to use the same memory, storage, and I/O bandwidth while optimizing their software licensing cost. 目前,计算成本(包括 OS 许可)与原始大小保持相同成本。At this time, the compute cost, which includes OS licensing, remains the same one as the original size. 有关详细信息,请参阅 Azure VM sizes for more cost-effective database workloads(适用于更经济高效数据库工作负荷的 Azure VM 大小)。For more information, see Azure VM sizes for more cost-effective database workloads.

名称Name vCPUvCPU 规格Specs
Standard_M8-2msStandard_M8-2ms 22 与 M8ms 相同Same as M8ms
Standard_M8-4msStandard_M8-4ms 44 与 M8ms 相同Same as M8ms
Standard_M16-4msStandard_M16-4ms 44 与 M16ms 相同Same as M16ms
Standard_M16-8msStandard_M16-8ms 88 与 M16ms 相同Same as M16ms
Standard_M32-8msStandard_M32-8ms 88 与 M32ms 相同Same as M32ms
Standard_M32-16msStandard_M32-16ms 1616 与 M32ms 相同Same as M32ms
Standard_M64-32msStandard_M64-32ms 3232 与 M64ms 相同Same as M64ms
Standard_M64-16msStandard_M64-16ms 1616 与 M64ms 相同Same as M64ms
Standard_M128-64msStandard_M128-64ms 6464 与 M128ms 相同Same as M128ms
Standard_M128-32msStandard_M128-32ms 3232 与 M128ms 相同Same as M128ms
Standard_E4-2s_v3Standard_E4-2s_v3 22 与 E4s_v3 相同Same as E4s_v3
Standard_E8-4s_v3Standard_E8-4s_v3 44 与 E8s_v3 相同Same as E8s_v3
Standard_E8-2s_v3Standard_E8-2s_v3 22 与 E8s_v3 相同Same as E8s_v3
Standard_E16-8s_v3Standard_E16-8s_v3 88 与 E16s_v3 相同Same as E16s_v3
Standard_E16-4s_v3Standard_E16-4s_v3 44 与 E16s_v3 相同Same as E16s_v3
Standard_E32-16s_v3Standard_E32-16s_v3 1616 与 E32s_v3 相同Same as E32s_v3
Standard_E32-8s_v3Standard_E32-8s_v3 88 与 E32s_v3 相同Same as E32s_v3
Standard_E64-32s_v3Standard_E64-32s_v3 3232 与 E64s_v3 相同Same as E64s_v3
Standard_E64-16s_v3Standard_E64-16s_v3 1616 与 E64s_v3 相同Same as E64s_v3
Standard_DS11-1_v2Standard_DS11-1_v2 11 与 DS11_v2 相同Same as DS11_v2
Standard_DS12-2_v2Standard_DS12-2_v2 22 与 DS12_v2 相同Same as DS12_v2
Standard_DS12-1_v2Standard_DS12-1_v2 11 与 DS12_v2 相同Same as DS12_v2
Standard_DS13-4_v2Standard_DS13-4_v2 44 与 DS13_v2 相同Same as DS13_v2
Standard_DS13-2_v2Standard_DS13-2_v2 22 与 DS13_v2 相同Same as DS13_v2
Standard_DS14-8_v2Standard_DS14-8_v2 88 与 DS14_v2 相同Same as DS14_v2
Standard_DS14-4_v2Standard_DS14-4_v2 44 与 DS14_v2 相同Same as DS14_v2

其他大小Other sizes

后续步骤Next steps

了解有关 Azure 计算单元 (ACU) 如何帮助跨 Azure SKU 比较计算性能的详细信息。Learn more about how Azure compute units (ACU) can help you compare compute performance across Azure SKUs.