| Bug #74283 | Non-covering secondary index scans degrade more in 5.7 than 5.6 | ||
|---|---|---|---|
| Submitted: | 8 Oct 2014 17:00 | Modified: | 29 May 2017 17:25 |
| Reporter: | Mark Callaghan | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S5 (Performance) |
| Version: | 5.7.5 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[8 Oct 2014 17:00]
Mark Callaghan
[10 Oct 2014 12:14]
MySQL Verification Team
Hello Mark,
Thank you for the bug report and test case.
Confirmed that the non-covering secondary index scan degrades more in 5.7.5 at 32 threads than 5.6.21.
I ran mysqlslap like this and stats are in following table:
X=1, 4, and 32
# non-covering secondary index scan
mysqlslap --concurrency=$X --create-schema=test1 --number-of-queries=100000 --create=iddl.sql --query="select k from foo FORCE INDEX(`xj`) where j >= 100 order by j limit 1000"
###################################
MySQL Version 5.7.5
###################################
-------------------------------------------------
Concurrency | non-covering secondary index scan |
-------------------------------------------------
1 | 123.684 sec |
4 | 70.811 sec |
32 | 104.539 sec |
-------------------------------------------------
###################################
MySQL Version 5.6.21
###################################
-------------------------------------------------
Concurrency | non-covering secondary index scan |
-------------------------------------------------
1 | 100.413 sec |
4 | 70.666 sec |
32 | 63.710 sec |
-------------------------------------------------
Average number of seconds to run all queries
Minimum number of seconds to run all queries
Maximum number of seconds to run all queries
-------------------------------------------------
Thanks,
Umesh
[29 May 2017 17:25]
Mark Callaghan
Is there an update for this?
