enhance: dimension of hot scheduler
Open
type/feature-request
- 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
After some tests, since each query consumes different resources, if we just try to make the number of queries consistent, there is a possibility that the number of queries is the same between each store, but the cpu is different.
Also, this may have something to do with the distribution of tables.
### Describe the feature you'd like
Perhaps we need to give feedback on scheduling based on cpu, or consider the dimension of the table, or we give them different weights
### Describe alternatives you've considered
### Teachability, Documentation, Adoption, Migration Strategy
Contributor guide
Assessment
This issue has not been assessed yet.