performance-tuning-practices: fix Scenario 2 CPU utilization value - #23791
performance-tuning-practices: fix Scenario 2 CPU utilization value#23791yahonda wants to merge 1 commit into
Conversation
|
Warning Review limit reachedNext included review available in 2 minutes. View limit detailsLimit details: You’ve used all 4 included reviews currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
What is changed, added or deleted? (Required)
Fixes a data inconsistency in the Summary section: comparing Scenario 5 with Scenario 2, the bullet stated the average TiDB CPU utilization "drops from 936% to 577%," but 936% is actually Scenario 3's value (per line ~174: "The TiDB average CPU utilization increases from 874% to 936%"), not Scenario 2's. Scenario 2's actual value is 874% (per line ~117: "the average TiDB CPU utilization drops from 925% to 874%"). This looks like a copy-paste error from the adjacent bullet ("Comparing Scenario 7 with Scenario 3 ... drops from 936% to 478%"), which correctly uses 936% since it's comparing against Scenario 3.
Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
AI agent involvement
Do your changes match any of the following descriptions?