Overview
cpu_quota_concurrency specifies the maximum number of active threads allowed for each CPU quota of a tenant.
Privilege requirements
Query parameters
Both the
systenant and all user tenants can query this parameter using theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview.Modify parameters
Both the
systenant and user tenants can modify this parameter.
Attributes
Attribute |
Description |
|---|---|
| Parameter type | DOUBLE |
| Default Value | 4 |
| Value range | [1, 20] |
| Modifiable | Yes, you can use theALTER SYSTEM SETstatements.
NoticeWe recommend that you avoid modifying this parameter. A smaller value may impact performance and even pose stability risks, while a larger value may increase memory usage and lead to excessive CPU load, posing certain risks. |
| Whether to restart the OBServer node for the change to take effect | No, the setting takes effect immediately. |
Usage instructions
The number of threads that can be processed concurrently in a tenant is controlled by the cpu_quota_concurrency and workers_per_cpu_quota parameters. The following condition must be met during configuration: workers_per_cpu_quota > cpu_quota_concurrency. Specifically:
workers_per_cpu_quota: The maximum number of worker threads that a tenant can allocate to each CPU. For more information aboutworkers_per_cpu_quota, see workers_per_cpu_quota.cpu_quota_concurrency: The maximum number of active threads allowed for each CPU quota of a tenant, that is, the concurrency level.
Configuration example
Set the maximum number of active threads allowed per CPU quota for a tenant to 4.
obclient> ALTER SYSTEM SET cpu_quota_concurrency=4;
References
worker thread