Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

executor: open childExec during execution for UnionExec #24899

Merged
merged 5 commits into from
Jun 10, 2021

Conversation

XuHuaiyu
Copy link
Contributor

@XuHuaiyu XuHuaiyu commented May 26, 2021

What problem does this PR solve?

Issue Number: close #21441

re-revert #21561

Problem Summary:

What is changed and how it works?

Proposal: xxx

What's Changed:
Before this commit, Union opens all the child executors during the Open phase.
This increases the overhead of buildRequest and the risk of OOM.

After this commit, the Open of childExec in Union is moved to the Next phase. The childExec be opened simultaneously is limited to tidb_executor_concurrency atmost.

How it Works:

Related changes

N/A

Check List

Tests

  • Integration test
  • Manual test
    Suppose we have a table t, it contains 100 partitions, each partition contains 10,000,000 tuples.
    The result of select * from t;
    Before:
    image
    After:
    The query works fine.

Side effects

  • The speed of UnionExec may decrease if the child of Union is larger than tidb_executor_concurrency.

Release note

  • Refine the execution mechanism UnionExec to reduce the overhead of UnionExec.

@XuHuaiyu XuHuaiyu added type/enhancement The issue or PR belongs to an enhancement. component/executor labels May 26, 2021
@XuHuaiyu XuHuaiyu requested a review from a team as a code owner May 26, 2021 02:50
@XuHuaiyu XuHuaiyu requested review from qw4990 and removed request for a team May 26, 2021 02:50
@ti-chi-bot ti-chi-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label May 26, 2021
@XuHuaiyu XuHuaiyu requested review from wshwsh12 and removed request for qw4990 May 26, 2021 02:50
@github-actions github-actions bot added the sig/execution SIG execution label May 26, 2021
@ti-chi-bot ti-chi-bot added the status/LGT1 Indicates that a PR has LGTM 1. label May 27, 2021
Copy link
Contributor

@ichn-hu ichn-hu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rest LGTM

// promised to exit when reaching here (e.childIDChan been closed).
var firstErr error
for i := 0; i <= e.mu.maxOpenedChildID; i++ {
if err := e.children[i].Close(); err != nil && firstErr == nil {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will close a not opened children cause problems here?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@XuHuaiyu PTAL

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like maxOpenedChildID can guarantee all children is opend.

Copy link
Contributor

@ichn-hu ichn-hu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ti-chi-bot
Copy link
Member

[REVIEW NOTIFICATION]

This pull request has been approved by:

  • ichn-hu
  • 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.

@ti-chi-bot ti-chi-bot added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Jun 10, 2021
@XuHuaiyu
Copy link
Contributor Author

/merge

@ti-chi-bot
Copy link
Member

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

Commit hash: cc7ac97

@ti-chi-bot ti-chi-bot added the status/can-merge Indicates a PR has been approved by a committer. label Jun 10, 2021
@ti-chi-bot ti-chi-bot merged commit 56b6797 into pingcap:master Jun 10, 2021
ti-srebot pushed a commit to ti-srebot/tidb that referenced this pull request Jun 10, 2021
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
@ti-srebot
Copy link
Contributor

cherry pick to release-5.1 in PR #25334

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/executor needs-cherry-pick-release-5.1 sig/execution SIG execution size/M Denotes a PR that changes 30-99 lines, ignoring generated files. status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support lazy open union children
6 participants