Overview
resource_hard_limit defines the CPU resource overprovisioning percentage. A value greater than 100 indicates overprovisioning is allowed.
Privilege requirements
Query parameters
Both the
systenant and all user tenants can query this parameter using theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview.Modify parameters
Only the
systenant can modify this parameter. User tenants cannot modify it.
Attributes
Attribute |
Description |
|---|---|
| Parameter type | Int |
| Default Value | 100 |
| Value range | [100, 10000] |
| Modifiable | Yes, you can use theALTER SYSTEM SETStatement modification. |
| Whether to restart the OBServer node for the change to take effect | No, the setting takes effect immediately. |
Usage instructions
Memory overprovisioning is no longer supported via the
resource_hard_limitparameter.resource_hard_limit: The overprovisioning ratio of theCPU_CAPACITYfor an OBServer node. On an OBServer node, the sum of theMAX_CPUvalues of all tenant units must not exceed the total CPU capacity plus the overprovisioning value:CPU_CAPACITY * resource_hard_limit.If
resource_hard_limit > 100is set, after overprovisioning takes effect, it only affects the resource (CPU) cap of the corresponding resource unit, not its resource floor. However, you must use the overprovisioning mechanism with extreme caution and ensure that the workload can consume resources in a way that avoids peak periods, to prevent system issues caused by 'overloading' the workload combined with resource overprovisioning.
Configuration example
Set the CPU overprovisioning percentage to 100.
obclient> ALTER SYSTEM SET resource_hard_limit = 100;