Dumpling Optimization

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: dumpling优化

| username: Geoffrey

[TiDB Usage Environment] Production Environment
[TiDB Version]
[Encountered Problem: Problem Phenomenon and Impact] Does dumpling put a lot of pressure on TiDB? Planning to export a table with 3.2 billion rows, will directly exporting it put too much pressure on TiDB? Currently planning to export 100,000 rows each time and then change the path to continue exporting, is this too conservative? Additionally, during testing, it was found that dumpling executes a slow SQL at the beginning, SELECT REGION_ID, START_KEY, END_KEY FROM INFORMATION_SCHEMA.TIKV_REGION_STATU, which takes a long time. Is there any way to optimize this?

| username: 像风一样的男子 | Original post link

Dumpling is a logical backup that consumes database resources. You can optimize the SQL by implementing pagination or switch to physical backup.

| username: tidb菜鸟一只 | Original post link

This is to check the region status within your cluster. You can see if this table is very large. If it has 3.2 billion records, it is not recommended to use dumpling. What do you need to export this data for?

| username: redgame | Original post link

Don’t be conservative, it’s better to import little by little.