Note
For V2.2.50 and later, this parameter is available starting with V2.2.50.
Description
server_cpu_quota_max specifies the maximum CPU quota that can be used by the system.
Privilege requirements
Query the parameter
You can use the
SHOW PARAMETERSstatement or viewGV$OB_PARAMETERSto query this parameter in thesystenant and in all user tenants.Modify the parameter
Only the
systenant can modify this parameter. User tenants cannot modify this parameter.
Attributes
| Attribute | Description |
|---|---|
| Type | Double |
| Default value | 0
Note
|
| Value range | [0, 16]
Note
|
| Modifiable | Yes. You can use the ALTER SYSTEM SET statement to modify the parameter. |
| Effective upon OBServer node restart | No. The setting takes effect immediately.
NoteThis parameter is available starting with V4.1.0, and the effective mode is changed from restart to immediate. |
Considerations
If this parameter is set to 0, it will be adaptively adjusted based on the size of cpu_count:
- If
cpu_countis less than 8 cores,server_cpu_quota_maxis adaptively set to 1 core. - If
cpu_countis between 8 and 16 cores,server_cpu_quota_maxis adaptively set to 2 cores. - If
cpu_countis between 16 and 32 cores,server_cpu_quota_maxis adaptively set to 3 cores. - If
cpu_countis 32 cores or more,server_cpu_quota_maxis adaptively set to 4 cores.
Examples
Adaptively set the maximum CPU quota.
obclient> ALTER SYSTEM SET server_cpu_quota_max=0;