Open Yui-Song opened 3 months ago
/type performance /type regression /sig planner /severity critical
/label affects-8.1 /remove-label may-affects-8.1 /remove-label may-affects-7.5 /remove-label may-affects-7.1 /remove-label may-affects-6.5 /remove-label may-affects-6.1 /remove-label may-affects-5.4
the increase in internal parse/compile time
is expect, as in https://github.com/pingcap/tidb/pull/50650/files#diff-5dde154d0b9319b8396cd0db16a82c86f265914566cc5fec9a58c81e4ae76594R260-R262, we changed the sql from a single table
query to a query with join
, and it runs every 300ms.
but the drop of QPS from 176K -> 163K
shouldn't be caused by this
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
OS & CPU info
2. What did you expect to see? (Required)
No performance regression
3. What did you see instead (Required)
No performance regression on CentOS Linux 7 (Core) with Intel(R) Xeon(R) Silver 4214R CPU @ 2.40GHz, but 7.3% performance regression in oltp_point_select on Kylin Linux with aarch64 v7.5.1 QPS 175680 v8.1.0 QPS 162811
v7.5.1
v8.1.0
4. What is your TiDB version? (Required)
8.1.0 commit d80e436e3c06004fc03ae79f896e89a2f7e2e2f6