-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
planner: reduce topn count to exclude non-skewed values | tidb-test=pr/2333 #53035
base: master
Are you sure you want to change the base?
Conversation
Hi @terry1purcell. Thanks for your PR. I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #53035 +/- ##
================================================
+ Coverage 72.5215% 74.5456% +2.0241%
================================================
Files 1506 1506
Lines 431006 431348 +342
================================================
+ Hits 312572 321551 +8979
+ Misses 99055 89861 -9194
- Partials 19379 19936 +557
Flags with carried forward coverage won't be shown. Click here to find out more.
|
@ZL91: adding LGTM is restricted to approvers and reviewers in OWNERS files. 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 kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ZL91 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@@ -1,124 +0,0 @@ | |||
<div align="center"> |
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.
Maybe PR shouldn't remove the README.md ?
@@ -2684,7 +2684,7 @@ var analyzeOptionDefault = map[ast.AnalyzeOptionType]uint64{ | |||
|
|||
var analyzeOptionDefaultV2 = map[ast.AnalyzeOptionType]uint64{ | |||
ast.AnalyzeOptNumBuckets: 256, | |||
ast.AnalyzeOptNumTopN: 500, |
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.
Could you please explain why we changed the TopNNum from 500 to 100 in comments ?
@@ -351,6 +351,7 @@ func testIssues24349(testKit *testkit.TestKit) { | |||
testKit.MustExec("create table t (a int, b int) partition by hash(a) partitions 3") | |||
testKit.MustExec("insert into t values (0, 3), (0, 3), (0, 3), (0, 2), (1, 1), (1, 2), (1, 2), (1, 2), (1, 3), (1, 4), (2, 1), (2, 1)") | |||
testKit.MustExec("analyze table t with 1 topn, 3 buckets") |
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.
Should we add some new test about the pruning logic in smaller table ? And check the topn number which has been pruned ?
What problem does this PR solve?
Issue Number: close #53111
Problem Summary:
What changed and how does it work?
PR includes 3 changes to reduce unnecessary TopN values:
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.