There is a 7% performance regression in Taobench benchmark
- Dominant language
- Go
- Stars
- 40.5k
- Forks
- 6.2k
- PR merge metrics
- PR metrics pending
Description
## Bug Report
Please answer these questions before submitting your issue. Thanks!
### 1. Minimal reproduce step (Required)
1. deploy a tidb cluster with 3 tidb + 3 tikv
2. run the workload_a of taobench benchmark
### 2. What did you expect to see? (Required)
No performance regression
### 3. What did you see instead (Required)
Update on 2024-07-09:
Workloads like select_random_ranges/select_random_points involving many coprocessor operations are also affected by the overhead caused by TiDB runtime events mentioned below.
The QPS of taobench:
baseline: v7.5.0, QPS = 27240
- 2023-12-10, QPS= 26931, commit https://github.com/pingcap/tidb/commit/899dfe8a7417a545a0c049c7d77876c8eaee5667, regression = 1.1%
- 2024-01-23, QPS= 25775, commit https://github.com/pingcap/tidb/commit/67fb41548da63491e324c09d57c53bb48a247d0d, regression=5.4%
- 2024-03-14, QPS= 24641, commit https://github.com/pingcap/tidb/commit/f8ac982ebf06198657f8943575fee0995890c390, regression=9.5%
- 2024-03-15, QPS= 24141, commit https://github.com/pingcap/tidb/commit/68c03cfb656436ab4082134872b8cf9afb86cd78, regression 11%
### 4. What is your TiDB version? (Required)
Contributor guide
Assessment
This issue has not been assessed yet.