Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: 如何配置参数符合最佳实践
[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Encountered Issues: Problem Phenomenon and Impact]
There are many configurable system parameters for concurrency control and hotspot handling in TiDB. How can we obtain configuration parameters that conform to best practices?
If hybrid deployment is not used, is the cluster deployed using TIUP by default considered best practice?
Is it still necessary to manually adjust according to the server’s CPU core count and memory capacity?
This is much more difficult compared to MySQL.
[Attachments: Screenshots/Logs/Monitoring]
First, use the default configuration and test each configuration parameter in combination with your business. The configuration that suits others’ business may not necessarily suit yours.
The default configuration of MySQL is also not the optimal configuration; it is adjusted gradually based on actual needs. If TiDB is not deployed in a mixed environment, using the default configuration is a good approach. You can make targeted adjustments if there are issues with the cluster.
If there is no mixed deployment, basically no need to change parameters.
In-depth research on TiDB principles + operating system principles + distributed principles + rich practical work experience. Based on your own situation, configure the best combination that suits your current status…
As mentioned above, best practices require gradual optimization.
It would be great if we could automatically adjust parameters based on historical load conditions to achieve autonomous database optimization. After all, parameter optimization is easier than SQL intelligent optimization.
The official should come up with a practical tutorial.
The default configuration is generally sufficient.
The default configuration will do.
|
username: 我是吉米哥
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: