When DataX Transfers Data, "Time Spent Sending Results" in Slow Queries is Very Long, How to Troubleshoot

Translated
1

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

Original topic: DataX传输数据时，慢查询中“发送结果耗时” 很长，如何排查

| username: Hacker_4BgeX58z

[Test Environment] Testing environment
[TiDB Version] V5.4.3
[Reproduction Path] Operations performed that led to the issue
[Encountered Issue: Phenomenon and Impact]
When reading data from TiDB using DataX, a slow query occurs. The slow query’s SQL execution time is “time taken to send results,” which is 1.9 minutes. This “time taken to send results” refers to the time taken to send the SQL execution results to the client. Who is this client referring to? Is it the time taken for TiDB to send the results to DataX? How should this issue be investigated?

image
image1380×522 58.5 KB

image
image1380×592 91.6 KB

[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

2
| username: hey-hoho | Original post link

The client here refers to the source that initiates the query, which is your dataX.
The long duration could be due to the result set being too large and requiring a long time to transfer, or the network between the database and the client being poor.

3
| username: Hacker_4BgeX58z | Original post link

Yes, the result set has 20,000 rows. The network between the database and the client has been checked and there are no issues. Is there a way to optimize the large result set to improve performance?

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

How long will it take to export these 20,000 records into a file and then transfer it from the database host to the client network?

5
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.