Parameter |
Description |
Recommended |
|---|---|---|
| workers_per_cpu_quota | This parameter * tenant max_cpu = the maximum number of threads that can be allocated to a tenant. | The maximum number of threads specified here is the allocated and available number, not the maximum number that can run concurrently. This parameter generally does not need to be adjusted. |
| net_thread_count | Number of Network Threads Receiving Client Requests | The change takes effect after a restart. Run the top -H command to check the utilization of MySQL I/O threads. If it exceeds 90%, the request-receiving threads may be a bottleneck. In this case, it is recommended to increase this parameter. If the utilization for all threads is less than 50%, it is recommended to decrease this parameter to reduce thread-switching overhead. |
| enable_early_lock_release | Enable Early Row Lock Release | It is recommended to enable this for hotspot row scenarios. |
| enable_monotonic_weak_read | Enable Monotonic Read | It is recommended to disable this feature for performance scenarios. |
| weak_read_version_refresh_interval | Weak Consistency Read Version Number Refresh Cycle | It is recommended to disable this feature for performance scenarios. |
| enable_sql_audit | Enable SQL Audit | It must be enabled in the production environment and can be disabled as appropriate in performance testing scenarios. |
| enable_perf_event | Enable Information Collection | It must be enabled in the production environment and can be disabled as appropriate in performance testing scenarios. |
| enable_record_trace_log | Enable Trace Log Feature | In a production environment with both the Perf Event and SQL Audit features enabled, this parameter can be disabled. |
| _trace_control_info | Enable end-to-end tracing | You can disable this feature for performance test scenarios as needed. |
CPU-related parameters
Share
Previous topic