OALP perftest tpch-2tiflash-50g& tpch-tiflash-50g result with total-avg-latency raise 15-20%

[stevenayu]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Deploy a tidb cluster with 3 TiDB (16c,48G) + 3 TiKV (16c,48G) + 2 TiFlash (16c,80G)
Compare the performance of v8.4.0 and v8.3.0 with TPCH benchmark

2. What did you expect to see? (Required)

No performance regression

3. What did you see instead (Required)

total-avg-latency raise 15-20%.

4. What is your TiFlash version? (Required)

v8.4.0 (cea728d)

[wuhuizuo]

/close

it is not caused by codes, but the llvm toolchain in building env.

[ti-chi-bot]

@wuhuizuo: Closing this issue.

In response to this:

/close

it is not caused by codes, but the llvm toolchain in building env.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[wuhuizuo]

/remove-type bug

[JaySon-Huang]

Caused by when the CI pipeline base image migrate from centos 7 to rockylinux 8. And the LLVM toolchain has been changed during the migration.

• feat(tiflash): gen build cache in merge ci for tiflash PingCAP-QE/ci#3187
• https://github.com/PingCAP-QE/artifacts/blob/4c3ca35b4241b78cce4490bac89c5103f2b3acd1/dockerfiles/cd/builders/tiflash/Dockerfile#L40-L46

Fixed by rebuilding the base image using the scripts in "/release-linux-llvm" and update the CI pipline

• chore(tiflash): update CI/CD pipelines PingCAP-QE/ci#3219