Parameter |
Description |
Recommendation |
|---|---|---|
| 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 number that can be allocated and used, not the maximum number that can run simultaneously. 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. You can run the top -H command to check the utilization of MySQL I/O threads. If the utilization exceeds 90%, it indicates that the thread receiving requests may have become a bottleneck. In this case, it is recommended to increase this parameter. If the utilization for all threads is less than 50%, it is suggested 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 | This parameter can be disabled in production environments where the Perf Event and SQL Audit features are enabled. |
| _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