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

resource_control: update static calibrate params #43541

Closed
wants to merge 3 commits into from

Conversation

HuSharp
Copy link
Contributor

@HuSharp HuSharp commented May 5, 2023

What problem does this PR solve?

Issue Number: ref #43212

Problem Summary:

What is changed and how it works?

Check List

Tests

  • Unit test

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

- The previous test data due to non-exclusive hard disk, io bandwidth is not full, so the tikv is not the bottleneck, the bottleneck is tidb.
But because tidb is easy to expand, tikv is more difficult to expand, so generally tikv is easy to bottleneck
Now the test data are basically playing full tikv, may be slightly more accurate
- cpu formula is ms, the previous calculation forgot to multiply by 1000

@ti-chi-bot
Copy link

ti-chi-bot bot commented May 5, 2023

[REVIEW NOTIFICATION]

This pull request has not been approved.

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
Copy link

ti-chi-bot bot commented May 5, 2023

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@ti-chi-bot ti-chi-bot bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. release-note-none Denotes a PR that doesn't merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels May 5, 2023
@ti-chi-bot ti-chi-bot bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels May 5, 2023
Signed-off-by: husharp <ihusharp@gmail.com>
HuSharp and others added 2 commits May 6, 2023 10:59
Signed-off-by: husharp <ihusharp@gmail.com>
Signed-off-by: husharp <jinhao.hu@pingcap.com>
@HuSharp HuSharp marked this pull request as ready for review May 8, 2023 10:01
@ti-chi-bot ti-chi-bot bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 8, 2023
@HuSharp
Copy link
Contributor Author

HuSharp commented May 15, 2023

@glorv @CabinfeverB @nolouch PTAL, thx!

Copy link
Member

@nolouch nolouch left a comment

Choose a reason for hiding this comment

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

Why need change them?

@HuSharp
Copy link
Contributor Author

HuSharp commented May 18, 2023

Why need change them?

  • The previous test data due to non-exclusive hard disk, io bandwidth is not full, so the tikv is not the bottleneck, the bottleneck is tidb.
    But because tidb is easy to expand, tikv is more difficult to expand, so generally tikv is easy to bottleneck.
    Now the test data are basically playing full tikv, may be slightly more accurate.
  • cpu formula is ms, the previous calculation forgot to multiply by 1000. @nolouch

@ti-chi-bot ti-chi-bot bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-none Denotes a PR that doesn't merit a release note. labels May 18, 2023
@HuSharp
Copy link
Contributor Author

HuSharp commented May 19, 2023

/review default

@ti-chi-bot
Copy link

ti-chi-bot bot commented May 19, 2023

@HuSharp:

Pull Request Summary

Title: Resource control: update static calibrate params

PR Description:

This PR aims to solve issue #43212. The key changes are the updates in calibration constants for several workloads. The new test data now generally plays full tikv and may be slightly more accurate. This also fixes a calculation error in the CPU formula, which was missing the factor of 1000 to obtain ms. Some formatting updates have been made along with a few comments.

Tests:

  • Unit test

Release Note:

- The previous test data due to non-exclusive hard disk, IO bandwidth is not full, so the tikv is not the bottleneck, the bottleneck is tidb.
But because tidb is easy to expand, tikv is more difficult to expand, so generally tikv is easy to bottleneck.
Now the test data are basically playing full tikv, may be slightly more accurate.
- CPU formula is ms, the previous calculation forgot to multiply by 1000.

Diff

+ Various calibration constant updates
+ CPU now multiplied by 1000 to convert into ms
+ Fixed comment typo and formatting issues

Review

The PR updates calibration parameters for several workloads, making them more accurate as a result of playing full tikv. Additionally, the CPU formula calculation was fixed by multiplying it with 1000 to obtain the correct unit. Formatting issues and comment typos were also corrected. Overall, the changes seem appropriate and should improve the performance monitoring and calibration procedure for TiDB.

Potential Problems

  1. The updated calibration constants were taken from new test data, and it is mentioned they are more accurate, but it's not clear how these values were obtained and whether they have been rigorously tested.

Suggestions

  1. Provide a detailed explanation of how the new calibration constants were obtained and if they have been thoroughly tested to validate their accuracy.

In response to this:

/review default

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 kubernetes/test-infra repository.

@ti-chi-bot
Copy link

ti-chi-bot bot commented May 19, 2023

PR needs rebase.

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 kubernetes/test-infra repository.

@ti-chi-bot ti-chi-bot bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 19, 2023
@codecov
Copy link

codecov bot commented Aug 7, 2023

Codecov Report

Merging #43541 (eef0191) into master (649fc4c) will increase coverage by 0.0071%.
Report is 1967 commits behind head on master.
The diff coverage is 100.0000%.

Additional details and impacted files
@@               Coverage Diff                @@
##             master     #43541        +/-   ##
================================================
+ Coverage   73.4725%   73.4796%   +0.0071%     
================================================
  Files          1190       1190                
  Lines        372738     373419       +681     
================================================
+ Hits         273860     274387       +527     
- Misses        81273      81446       +173     
+ Partials      17605      17586        -19     

Copy link

ti-chi-bot bot commented Dec 19, 2023

@HuSharp: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-integration-ddl-test eef0191 link true /test pull-integration-ddl-test

Full PR test history. Your PR dashboard.

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 kubernetes/test-infra repository. I understand the commands that are listed here.

@HuSharp
Copy link
Contributor Author

HuSharp commented Dec 20, 2023

maybe stale data

@HuSharp HuSharp closed this Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants