Microsoft Announces new Azure VM sizes for more cost-effective database workloads
Our customers told us that their database workloads like SQL Server or Oracle often require high memory, storage, and I/O bandwidth, but not a high core count. Many database workloads they are running are not CPU-intensive. They want a VM size that enables them to constrain the VM vCPU count to reduce the cost of software licensing, all while maintaining the same memory, storage, and I/O bandwidth.
We are excited to announce the latest versions of our most popular VM sizes (DS, ES, GS, and MS), which constrain the vCPU count to one half or one quarter of the original VM size, while maintaining the same memory, storage and I/O bandwidth. We have marked these new VM sizes with a suffix that specifies the number of active vCPUs to make them easier for you to identify.
For example, the current VM size Standard_GS5 comes with 32 vCPUs, 448GB mem, 64 disks (up to 256 TB), and 80,000 IOPs or 2 GB/s of I/O bandwidth. The new VM sizes Standard_GS5-16 and Standard_GS5-8 comes with 16 and 8 active vCPUs respectively, while maintaining the rest of the specs of the Standard_GS5 in regards to memory, storage, and I/O bandwidth.
The licensing charged for SQL Server or Oracle will be constrained to the new vCPU count, and other products should be charged based on the new vCPU count. All of this results in a 50% to 75% increase in the ratio of the VM specs to active (billable) vCPUs. These new VM sizes that are only available in Azure, allowing workloads to push higher CPU utilization at a fraction of the (per-core) licensing cost. At this time, the compute cost, which includes OS licensing, remains the same one as the original size.
Read the entire article here, Announcing new Azure VM sizes for more cost-effective database workloads | Blog
Via the fine folks at Microsoft.