Fix inaccurate memory tracking in IndexJoin/IndexHashJoin #34417
Labels
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 the 5.4.x(LTS) versions.
affects-6.0
component/executor
severity/major
sig/execution
SIG execution
type/bug
The issue is confirmed as a bug.
Running the query q3,q7,q8 of workload tpch-50g, TiDB will tracked memory usgae more than actual memory usage.
For example, q8:
Plan:
Grafana: (Running the sql 5 times)

We can see the memory usage of IndexJoin/IndexHashJoin is more than 2GB, but the actual memory usage is low.
The text was updated successfully, but these errors were encountered: