When migrating a MySQL database to TiDB using the DM tool, can rate limiting configurations be added on DM? For example, limiting network traffic or restricting the number of CPU cores used?
【TiDB Usage Environment】Production\Test Environment\POC
【TiDB Version】
【Encountered Problem】
【Reproduction Path】What operations were performed that led to the problem
【Problem Phenomenon and Impact】
【Attachments】
Corresponding module’s Grafana monitoring (if any, such as BR, TiDB-binlog, TiCDC, etc.)
Corresponding module logs (including logs from 1 hour before and after the issue)
If the question is related to performance optimization or troubleshooting, please download and run the script. Please select all and copy-paste the terminal output results for upload.
You can refer to the official website DM configuration optimization to set and adjust parameters such as rows, chunk-filesize, pool-size, batch, etc., to limit the export and import speed:
I looked at the configuration on the official website mentioned by the teacher above, but I still don’t quite understand which parameter limits the network traffic between MySQL and TiDB?
Because it’s a production environment, I don’t want the network card traffic to be fully utilized, as it might affect other services.
This parameter primarily affects the TiDB side. Additionally, this parameter only pertains to the size of the result set involved in the SQL, and it doesn’t have much to do with network throttling.
What you mentioned is incremental, which should have an indirect effect, but I mainly want to limit the network transmission traffic during DM full migration to reduce the impact on the business.
|
username: Johnpan
|
username: 
|
username: 
|
username: 
|
username: 
|
username: 
|
username: