Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Top SQL is not reporting correctly in the Sysbench PointSelect workload #33499

Open
breezewish opened this issue Mar 28, 2022 · 0 comments
Open
Assignees
Labels
affects-6.0 severity/moderate sig/diagnosis SIG: Diagnosis type/bug The issue is confirmed as a bug.

Comments

@breezewish
Copy link
Member

breezewish commented Mar 28, 2022

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

sysbench oltp_point_select prepare --mysql-host=127.0.0.1 --mysql-port=4000 --mysql-user=root --db-driver=mysql --mysql-db=test --threads=400 --time=600 --report-interval=10
sysbench oltp_point_select run --mysql-host=127.0.0.1 --mysql-port=4000 --mysql-user=root --db-driver=mysql --mysql-db=test --threads=400 --time=300 --report-interval=10

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

Top SQL shows exactly the same Top N sql statements for each run.

3. What did you see instead (Required)

The Second Top sql statements changes each time when the cluster is re-deployed. It even shows that CREATE TABLE statement is taking a lot of CPU, which is definitely incorrect.

wWwcCrB6lI
qDKTIys9DR
oxhhaO8tvl
origin_img_v2_cde2911b-b79b-4a0c-b57f-df95cc1b63cg

4. What is your TiDB version? (Required)

master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.0 severity/moderate sig/diagnosis SIG: Diagnosis type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

3 participants