Dongpo Liu
Dongpo Liu
From another test env: ```sql explain analyze SELECT version, table_id, modify_count, count, snapshot from mysql.stats_meta where version > 462914510819164514 order by version; +-----------------------+----------+---------+-----------+------------------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+--------------------------------------------------+---------+---------+ | id | estRows | actRows |...
More background: # Investigating TiDB performance in analytics_benchmark V2 ## Background We observed that TiDB's query performance was extremely poor in https://github.com/toddstoffel/analytics_benchmark, so we conducted an analysis and produced this...
I think this is a false positive feedback: https://github.com/pingcap/docs/actions/runs/18338863546/job/52229172406?pr=21873
We should use index range scan here. We could hardcode the hint in the code.
Another slow query from a different cluster: ```sql | id | estRows | estCost | actRows | task | access object | execution info | operator info | memory |...
We recognized two patterns: ## total_suspend_time too long ```sql | id | estRows | estCost | actRows | task | access object | execution info | operator info | memory...