-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
resource_control supports calibrate resource #43212
Labels
type/feature-request
Categorizes issue or PR as related to a new feature.
Comments
nolouch
added
the
type/feature-request
Categorizes issue or PR as related to a new feature.
label
Apr 19, 2023
nolouch
changed the title
resource_control: support calibrate resource
resource_control supports calibrate resource
Apr 19, 2023
9 tasks
1 task
1 task
12 tasks
12 tasks
12 tasks
CabinfeverB
added a commit
to ti-chi-bot/tidb
that referenced
this issue
Jul 5, 2023
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Request
Add new statement
calibrate resource
to estimate the total Request-Units(RU) of the current cluster.Because the total ru usage is related to workload resource consumption, so the maximum RU can be different with the different workloads. Thus, the maximum RU estimated by this PR is based on a given workload -- TPC-C, and we may support another workload (e.g. sysbench) in the future.
In general, the bottle of a cluster can be one of TiDB CPU, TiKV CPU, and TiKV IO Bandwidth. Currently, we can get the exact IO bandwidth and for most workloads, it is unlikely to be the bottleneck. So here, we only consider TiDB CPU or TiKV CPU as the bottleneck.
And also we consider needing to make the calibrate according to the actual workload to make it more accurate.
Issuse
The text was updated successfully, but these errors were encountered: