*: Refine execution summary with ExecutorStatisticsCollector

[ywqzzy]

What problem does this PR solve?

Issue Number: ref #5900 #6518

Problem Summary:

What is changed and how it works?

In previous implementation, ExecutionSummaryCollector traverse through all profilingStreams to collect local execution info.
While the ExecutorsStatisticsCollector do the same job for mpp tracing.
As a result, we can use ExecutorsStatisticsCollector to collect local execution info instead.

The change contains:

1. use ExecutorsStatisticsCollector to fill execution summary.
2. allow ExecutorsStatisticsCollector to collect profile for list based executors and cop tasks.
3. Refine JoinImpl to add join build time.
4. add more tests for list-based executor (from tispark) and tree-based executor (from tidb), add test for execution summary with planner and QueryBlockInterpreter.
5. fwd declare some DAGContext to make the compile faster.

Check List

Tests

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

use test;
create table t(a int);
alter table t set tiflash replica 1;
insert into t values(1),(2),(3),(4);
create table t2(a int);
insert into t2 values(1),(2);
alter table t2 set tiflash replica 1;

set tidb_enforce_mpp=true;
insert into t select * from t;
insert into t select * from t;
insert into t select * from t;
insert into t select * from t;
insert into t select * from t;
insert into t select * from t;
insert into t select * from t;
insert into t select * from t;
insert into t select * from t;

explain analyze select * from t, t2;
explain analyze select * from t;
explain analyze select count(a) from t group by a;
explain analyze select count(a) from t;
explain analyze select * from t, t2 where t.a = t2.a;

• 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

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• SeaRise
• yibin87

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.

[SeaRise]

This treatment is wrong
From https://github.com/pingcap/tiflash/pull/6995/files#diff-8afda9cf273246b0b526e551688e59abad0ac41f2803a82e1342eb15bf1c1a4bL88-L109, here also need to add the execute time of all join build streams that executed before.

[ywqzzy]

/run-all-tests

[SeaRise]

Others LGTM

[SeaRise]

lgtm

[ywqzzy]

/run-all-tests

[yibin87]

LGTM

[ywqzzy]

/merge

[ti-chi-bot]

@ywqzzy: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

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

Commit hash: dfa1d0a

[ywqzzy]

/merge

[ti-chi-bot]

@ywqzzy: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

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

Commit hash: 05ebf5a

[ywqzzy]

/run-unit-tests

[ti-chi-bot]

@ywqzzy: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

trigger some heavy tests which will not run always when PR updated.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.