This again, is not to be confused with constrained VM series, as it only covers the vCPU available and that can be counted on the VM. Microsoft Support can disable hyperthreading, (or multithreading) on our vCPUs, which some customers choose to do to save on licensing at the cost of performance and paying more on monthly infrastructure. The third topic stems around the need to distinguish between enabled and disabled in the licensing documentation. Oracle recently updated their documentation around third party cloud support and licensing, replacing hyperthreading to go to the more generic term for any CPU that can produce multiple threads per CPU. We’ll also discuss the continual confusion around the terms of hyperthreading and multithreading. Sometimes the confusion is on the term, “constrained”, (I would have named this VM type, “Same CPU, bigger chassis”.) We’ll go over how we can confirm how many vCPU is on the VM, including comparing a standard VM with 16 vCPU and a constrained 8-vCPU with the 16-vCPU chassis, demonstrating the vCPU count validation between both of them. Numerous times I’ve experienced misunderstanding on licensing around constrained vCPU VMs.

Oracle cpu