On overprovisioned Dedicated Hosts, increasing the CPU overcommit ratio adds more available vCPUs to the host, so you can deploy more ECS instances on a single host and reduce deployment cost. This applies to workloads that tolerate moderate CPU contention, such as development environments, batch jobs, or low-traffic services.
Prerequisites
Before you begin, make sure that:
The Dedicated Host is an overprovisioned type, such as g6s, c6s, r6s, g7s, or r7s. For more information, see Dedicated host types.
All ECS instances on the Dedicated Host are in the Stopped state. The modification requires all instances to be stopped.
Configure the CPU overcommit ratio
Log on to the ECS console.
In the left-side navigation pane, choose Instances & Images >
> Dedicated Hosts.In the top navigation bar, select the region and resource group of the resource you want to manage.
Select the Dedicated Host, then in the upper-left corner of the Host tab, choose
> Modify DDH Info.
In the Modify DDH Information dialog box, set the Custom CPU Oversold Ratio.
ImportantA higher CPU overcommit ratio provides more active vCPUs but increases CPU resource contention, which can degrade performance stability. Set the ratio based on your actual workload — use lower values for latency-sensitive or CPU-intensive services.
The Custom CPU Oversold Ratio accepts values from 1 to 5. Available vCPUs are calculated as:
Available vCPUs = CPU cores x 2 x CPU overcommit ratio
For example, a g6s Dedicated Host has 52 CPU cores. At a CPU overcommit ratio of 2, the available vCPUs are 52 x 2 x 2 = 208.
Click OK.
API alternative
To configure the CPU overcommit ratio programmatically, call the ModifyDedicatedHostAttribute API operation.