Bug #82524 | Significant innodb load performance regression since version 5.5 | ||
---|---|---|---|
Submitted: | 10 Aug 2016 8:36 | Modified: | 25 Aug 2016 8:22 |
Reporter: | Mark Kirkwood | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S5 (Performance) |
Version: | 5.6, 5.6.32, 5.7.14 | OS: | Ubuntu (16.04) |
Assigned to: | CPU Architecture: | Any |
If the data you need to attach is more than 50MB, you should create a compressed archive of the data, split it to 50MB chunks, and upload each of them as a separate attachment.
To split a large file:
- On *nix platforms use the split command e.g.
split -b 50MB <my_large_archive> <my_split_archive_prefix>
- On windows use WinZip or a similar utility to split the large file
[10 Aug 2016 8:46]
Mark Kirkwood
[10 Aug 2016 8:47]
Mark Kirkwood
Perf output for mysql 5.6
Attachment: perf.out.5.6 (application/octet-stream, text), 524.01 KiB.
[17 Aug 2016 5:56]
Mark Kirkwood
5.5 config
Attachment: my-5.5.cnf (application/octet-stream, text), 5.04 KiB.
[17 Aug 2016 5:57]
Mark Kirkwood
5.7 config
Attachment: my-5.7.cnf (application/octet-stream, text), 5.17 KiB.
[17 Aug 2016 5:57]
Mark Kirkwood
Data generation
Attachment: gendata.py (text/x-python), 1.82 KiB.
[18 Aug 2016 9:00]
Umesh Shastry
test results
Attachment: 82524.results (application/octet-stream, text), 12.77 KiB.