-
Notifications
You must be signed in to change notification settings - Fork 704
sql-statement: calibrate resource support workload #13270
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
Conversation
[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 submitting an approval review. |
The `CALIBRATE RESOURCE` statement is used to estimate and output the ['Request Unit (RU)`](/tidb-resource-control#what-is-request-unit-ru) capacity of the current cluster. | ||
The `CALIBRATE RESOURCE` statement is used to estimate and output the ['Request Unit (RU)`](/tidb-resource-control#what-is-request-unit-ru) capacity of the current cluster. TiDB provides two methods for estimation: | ||
|
||
- Method 1: view the capacity within a specified time window depending on the actual workload. The following constraints apply to improve the accuracy of the estimation: |
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.
- Method 1: view the capacity within a specified time window depending on the actual workload. The following constraints apply to improve the accuracy of the estimation: | |
- Method 1: estimate the capacity based on the actual workload during a specified time window. The following constraints apply to improve the accuracy of the estimation: |
Co-authored-by: Hu# <ihusharp@gmail.com>
- You have `SUPER` or `RESOURCE_GROUP_ADMIN` privilege. | ||
- You have the `SELECT` privilege for all tables in the `METRICS_SCHEMA` schema. | ||
|
||
## Parameters |
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.
## Parameters | |
## Estimation methods |
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.
rest LGTM
Co-authored-by: Roger Song <roger.song@pingcap.com>
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.
LGTM!
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.
Rest LGTM
Co-authored-by: Aolin <aolinz@outlook.com>
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 1437d97
|
What is changed, added or deleted? (Required)
as tittle
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?