the pushed operator should scale with regions & index lookup will issue too much cop tasks.
Open
affects-7.5
report/customer
sig/planner
type/enhancement
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Enhancement
the real table regions is about 4000+, while the index lookup issues 500M cop tasks cost too much time.
* the pushed operator's cost should multiple region num?
* we should make a trade-off between row count est and cop task number, especially for index lookup.
* a kind of regionScan(distinguished from rowIDScan and FullScan) should be tested after discussion with @chenshuang
Contributor guide
Assessment
This issue has not been assessed yet.