Engine Switching Issues

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 引擎切换问题

| username: Running

When querying based on the time field with millions of data tables that have the TiFlash engine enabled, the default query uses TiKV. Forcing the query to use TiFlash is significantly faster than using TiKV. Is there a problem with the CBO optimizer?

2
| username: ShawnYan | Original post link

TiDB version? Number of TiFlash replicas? Execution plan?

3
| username: tidb菜鸟一只 | Original post link

Are the statistics accurate?

4
| username: Kongdom | Original post link

Please send the query statement, it is probably an issue with the statement.

5
| username: liuis | Original post link

Without any information, others can’t help either.

6
| username: Running | Original post link

Statistics and re-statistics worked.

7
| username: Running | Original post link

Regarding the engine switching issue, I feel it still needs optimization. I am currently using a separate node with the TiFlash engine to handle complex queries.

8
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.