Long Response Time for Single Table Query

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

Original topic: 单表查询发送结果耗时长

| username: 像风一样的男子

[Test Environment for TiDB]
[TiDB Version] 5.4.3
[Encountered Issue: Phenomenon and Impact]
Querying tens of thousands of rows from a single table, most of the time is consumed in sending the results. How can this be optimized?
[Attachments: Screenshots/Logs/Monitoring]


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

Try running the SQL on the server to check the execution time.

| username: ohammer | Original post link

Is the amount of returned data large? Try adding a limit to restrict the number of returned rows and see the time consumption.

| username: Tank001 | Original post link

It feels like the above picture should be more complete. Maybe an index is missing, t_biake_rec, or the result data volume is large.

| username: ti-lanse | Original post link

The final estRows is more than seventy thousand, let’s paginate it.