Note
This parameter is available starting with V4.2.1.
Description
ttl_thread_score specifies the weight of the thread time slice for TTL tasks.
Privilege requirements
Query the parameter
sysand all user tenants can query the value of this parameter by using theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview.Modify the parameter
sysand user tenants can modify this parameter.
Attributes
| Attribute | Description |
|---|---|
| Type | Int |
| Default value | 0 indicates that the default number of threads is used, which is 2 by default. |
| Value range | [0, 100] |
| 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. |
Considerations
You can adjust the weight of the thread time slice for TTL DAGs to modify the proportion of the thread time slice used by TTL tasks. If you find that the TTL tasks run slowly, you can increase the value of ttl_thread_score to an appropriate value. We recommend that you double the value each time.
Examples
Set the weight of the thread time slice for TTL tasks to 4 in all user tenants.
obclient> ALTER SYSTEM SET ttl_thread_score = 4 tenant = all_user;