tikv / tikv/pd

Reduce the impact of GC in hot region scheduler

Open
#3,084 3 comments 0 reactions 0 assignees View on GitHub
difficulty/medium high-performance status/discussion-wanted type/enhancement
Dominant language
Go
Stars
1.2k
Forks
783
Avg merge
5d 21h
Merged PRs (30d)
36

Description

## Feature Request

### Describe your feature request related problem
Do `oltp_update_non_index`, and 5* TiKV with 5x2large Node (1.1TB gp2), the metrics show as:

![image](https://user-images.githubusercontent.com/6428910/96422761-04e5e100-122b-11eb-9e1d-1e8e61fd426a.png)
![image](https://user-images.githubusercontent.com/6428910/96422832-1e872880-122b-11eb-9f04-b1042f127137.png)
![image](https://user-images.githubusercontent.com/6428910/96422891-3068cb80-122b-11eb-8dbc-55dab9312113.png)

### Describe the feature you'd like
Reduce the operator of hotspot scheduling caused by GC

### Describe alternatives you've considered
- Exclude the GC write/read keys from the statistic
- Consider a way to reduce the impact the internal mechanism

## Score

- 3000

## Mentor(s)

- @lhy1024
- @nolouch

### Recommended Skills
- Go
- Rust

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.