memory.reArrangeFallback uses 50% of the time for SELECT with 8k partitions #30353
Labels
affects-5.0
This bug affects 5.0.x versions.
affects-5.1
This bug affects 5.1.x versions.
affects-5.2
This bug affects 5.2.x versions.
affects-5.3
This bug affects 5.3.x versions.
affects-5.4
This bug affects 5.4.x versions.
affects-6.0
severity/major
sig/execution
SIG execution
type/bug
The issue is confirmed as a bug.
Bug Report
Profiling a simple
SELECT * FROM t
for a partitioned table with maximum number of partitions spends around half the time in thememory.reArrangeFallback
tracking function.1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
The result to be given within milliseconds at least (MySQL does it in 0.1 second)
3. What did you see instead (Required)
The SELECT query took 1 second
4. What is your TiDB version? (Required)
Profiles:
The text was updated successfully, but these errors were encountered: