-
Notifications
You must be signed in to change notification settings - Fork 690
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
SQL variables: add a new variable tidb_enable_parallel_apply
#5092
SQL variables: add a new variable tidb_enable_parallel_apply
#5092
Conversation
/translation from-docs-cn |
/label needs-cherry-pick-5.0 |
@qw4990: In response to this: 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. |
/LGTM |
@qw4990: In response to this:
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. |
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
system-variables.md
Outdated
|
||
- Scope: SESSION | GLOBAL | ||
- Default value: 0 | ||
- This variable controls whether to enable the Apply operator concurrency, and the number of concurrency is controlled by the `tidb_executor_concurrency` variable. The Apply operator is used to process correlated subqueries and has no concurrency by default, so the execution speed is slow. Enable the Apply concurrency switch can increase concurrency and speed up execution. Currently, this variable defaults to be disabled. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- This variable controls whether to enable the Apply operator concurrency, and the number of concurrency is controlled by the `tidb_executor_concurrency` variable. The Apply operator is used to process correlated subqueries and has no concurrency by default, so the execution speed is slow. Enable the Apply concurrency switch can increase concurrency and speed up execution. Currently, this variable defaults to be disabled. | |
- This variable controls whether to enable concurrency for the `Apply` operator. The number of concurrencies is controlled by the `tidb_executor_concurrency` variable. The `Apply` operator processes correlated subqueries and has no concurrency by default, so the execution speed is slow. Setting this variable value to `1` can increase concurrency and speed up execution. Currently, concurrency for `Apply` is disabled by default. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Joyinqin Please see this comment.
Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
/label require-LGT1 |
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by writing |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: a56f022
|
/merge |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-5.0 in PR #5120 |
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
tidb_enable_parallel_apply
docs-cn#4819Do your changes match any of the following descriptions?