distsql,executor: using paging protocol for all coprocessor requests

[tiancaiamao]

What problem does this PR solve?

Issue Number: close #35067

Problem Summary:

What is changed and how it works?

Set paging when building the distsql request, for all executors.
In the past we only do that for IndexLoopUp.

There is still a switch tidb_enable_paging to control the behavior. The default value is still false.
I want coprocessor paging to be the default implementation for all cases, but let's do it step by step.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

mysql> select count(*) from sbtest1;
+----------+
| count(*) |
+----------+
|  7425577 |
+----------+
1 row in set (0.44 sec)

Use this PR, and then set @@tidb_enable_paging=1 to see the difference:

mysql -h 127.0.0.1 -u root -P 4000  -e 'select * from  (select * from sbtest.sbtest1 union all select * from sbtest.sbtest2 union all select * from sbtest.sbtest3 union all select * from sbtest.sbtest4 union all select * from sbtest.sbtest5 union all select * from sbtest.sbtest6 union all select * from sbtest.sbtest7 union all select * from sbtest.sbtest8)' > /dev/null

mysql -h 127.0.0.1 -u root -P 4000  -e 'set @@tidb_enable_paging=1; select * from  (select * from sbtest.sbtest1 union all select * from sbtest.sbtest2 union all select * from sbtest.sbtest3 union all select * from sbtest.sbtest4 union all select * from sbtest.sbtest5 union all select * from sbtest.sbtest6 union all select * from sbtest.sbtest7 union all select * from sbtest.sbtest8)' > /dev/null

Before vs After

It reduce a lot memory footprint ... although we need to handle channel capacity #34849 to completely solve the problem.

• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• XuHuaiyu
• wshwsh12

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[sre-bot]

Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/1d0cc0e321f871c0168f0eb2e0f355fd0b0b850e

[tiancaiamao]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 5eb7151

[sre-bot]

TiDB MergeCI notify

✅ Well Done! New fixed [1] after this pr merged.

CI Name	Result	Duration	Compare with Parent commit
idc-jenkins-ci-tidb/integration-common-test	✅ all 11 tests passed	13 min	Fixed
idc-jenkins-ci/integration-cdc-test	🟢 all 35 tests passed	28 min	Existing passed
idc-jenkins-ci-tidb/integration-ddl-test	🟢 all 6 tests passed	7 min 33 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-2	🟢 all 28 tests passed	6 min 22 sec	Existing passed
idc-jenkins-ci-tidb/common-test	🟢 all 12 tests passed	6 min 14 sec	Existing passed
idc-jenkins-ci-tidb/tics-test	🟢 all 1 tests passed	5 min 52 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-1	🟢 all 26 tests passed	5 min 33 sec	Existing passed
idc-jenkins-ci-tidb/integration-compatibility-test	🟢 all 1 tests passed	3 min 14 sec	Existing passed
idc-jenkins-ci-tidb/mybatis-test	🟢 all 1 tests passed	2 min 53 sec	Existing passed
idc-jenkins-ci-tidb/plugin-test	🟢 build success, plugin test success	4min	Existing passed