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
Tracking Issue for Load Base Split Improvement #12063
Labels
type/enhancement
Type: Issue - Enhancement
Comments
This was referenced May 20, 2022
ti-chi-bot
added a commit
that referenced
this issue
May 25, 2022
ref #12063 raftstore: refine some code of the PD and SplitController Signed-off-by: JmPotato <ghzpotato@gmail.com> Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
YuJuncen
pushed a commit
to YuJuncen/tikv
that referenced
this issue
May 26, 2022
ref tikv#12063 raftstore: refine some code of the PD and SplitController Signed-off-by: JmPotato <ghzpotato@gmail.com> Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io> Signed-off-by: Yu Juncen <yujuncen@pingcap.com>
This was referenced Jun 30, 2022
ti-chi-bot
added a commit
that referenced
this issue
Jul 6, 2022
ti-chi-bot
pushed a commit
that referenced
this issue
Jul 11, 2022
ref #12063 Update the Load Base Split metrics event to distinguish more cases. Signed-off-by: JmPotato <ghzpotato@gmail.com>
This was referenced Jul 12, 2022
ti-chi-bot
added a commit
that referenced
this issue
Jul 13, 2022
ref #12063 Fix the building warning caused by the feature cfg. Signed-off-by: JmPotato <ghzpotato@gmail.com> Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
ekexium
pushed a commit
to ekexium/tikv
that referenced
this issue
Jul 13, 2022
…or registration mechanism (tikv#12942) ref tikv#12063, ref tikv#12593 Introduce the new split config and CPU collector registration mechanism. Signed-off-by: JmPotato <ghzpotato@gmail.com>
ekexium
pushed a commit
to ekexium/tikv
that referenced
this issue
Jul 13, 2022
ref tikv#12063, ref tikv#12593, ref tikv#12942 Introduce the CPU-based Load Base Split strategy. Signed-off-by: JmPotato <ghzpotato@gmail.com> Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
ekexium
pushed a commit
to ekexium/tikv
that referenced
this issue
Jul 13, 2022
…tegy (tikv#12969) ref tikv#12063 Add some test cases for the CPU-based Load Base Split strategy. Signed-off-by: JmPotato <ghzpotato@gmail.com> Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
This was referenced Jul 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As mentioned in tikv/pd#4588, Load Base Split can not work well in most or pure scan scenarios. We need to introduce more statistical dimensions to the Load Base Split decision process, such as statistics related to the read CPU usage. This is the tracking issue for some related work.
Steps
gRPC Poll CPU utilization collecting (Collect the gRPC Poll CPU utilization of each read request #12139)Unresolved Questions
Cost Model: A cost model is needed to evaluate and determine the split effect between the read pool and gRPC poll CPU.The text was updated successfully, but these errors were encountered: