server_cpu_quota_max

Last Updated:2026-09-04 11:28:24

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.

Query the parameter

You can use the SHOW PARAMETERS statement or view GV$OB_PARAMETERS to query this parameter in the sys tenant and in all user tenants.
Modify the parameter

Only the sys tenant can modify this parameter. User tenants cannot modify this parameter.

Attribute	Description
Type	Double
Default value	0 Note This parameter is available starting with V4.0.0, and the default value is adjusted from 5 to 1. This parameter is available starting with V4.2.1, and the default value is adjusted from 1 to 0.
Value range	[0, 16] Note This parameter is available starting with V4.0.0, and the value range is adjusted from [0, 16] to [1, 16]. This parameter is available starting with V4.2.1, and the value range is adjusted from [1, 16] to [0, 16].
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. Note This parameter is available starting with V4.1.0, and the effective mode is changed from restart to immediate.

If this parameter is set to 0, it will be adaptively adjusted based on the size of cpu_count:

If cpu_count is less than 8 cores, server_cpu_quota_max is adaptively set to 1 core.
If cpu_count is between 8 and 16 cores, server_cpu_quota_max is adaptively set to 2 cores.
If cpu_count is between 16 and 32 cores, server_cpu_quota_max is adaptively set to 3 cores.
If cpu_count is 32 cores or more, server_cpu_quota_max is adaptively set to 4 cores.

Adaptively set the maximum CPU quota.

obclient> ALTER SYSTEM SET server_cpu_quota_max=0;

Previous topic

Next topic