- Services: Compute
- Release Date: July 10, 2020
The service limits for Compute instances now apply at the OCPU level for a shape series, instead of at the individual shape level. Also, core-based compartment quotas for Compute shapes are now available. These updates let you manage your Compute resources based on OCPUs and GPUs, the same way that Compute resources are billed.
Previously, the service limits for Compute instances applied to each shape. For example, there were separate service limits for VM.Standard2.1 shapes, VM.Standard2.2 shapes, and BM.Standard2.52 shapes.
Now, the service limits for Compute instances cover the total number of OCPUs or GPUs for all shapes in a shape series. In addition, the service limits are aggregated for similar virtual machine (VM) and bare metal series. For example, one of the new per-core service limits covers the total number of OCPUs for all shapes in the VM.Standard2 and BM.Standard2 series.
Your existing service limits are being migrated by Oracle Cloud Infrastructure to the equivalent per-core limit. For example, say that you have a service limit of 1 for a hypothetical shape called SeriesA.ShapeX.5cores, and a service limit of 2 for a different hypothetical shape called SeriesA.ShapeY.10cores. Your new Series A service limit is 25 OCPUs total (5 OCPUs times 1 shapeX, plus 10 OCPUs times 2 shapeY), and you can allocate this limit across both the SeriesA.ShapeX.5cores and SeriesA.ShapeY.10cores shapes.
Although you can continue to use the shape-based service limits, these limits are converted to the equivalent per-core values. You can view the deprecated shape-based service limits by selecting the Show deprecated limits check box on the Limits, Quotas and Usage page in the Console.
For more information about the new service limits, see Service Limits.
You can now set compartment quotas for Compute shapes to cover the total number of OCPUs or GPUs for all shapes in a shape series, aggregated for similar VM and bare metal series. The per-core compartment quotas are available at the availability domain scope.
There are no changes to the existing compartment quotas that cover individual shapes.
For more information about the new compartment quotas, see Compartment Quotas.