| Bug #54914 | InnoDB: performance drop with innodb_change_buffering=all | ||
|---|---|---|---|
| Submitted: | 30 Jun 2010 13:08 | Modified: | 26 Oct 2010 21:52 |
| Reporter: | Alexey Stroganov | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S5 (Performance) |
| Version: | 5.5.5 | OS: | Any |
| Assigned to: | Marko Mäkelä | CPU Architecture: | Any |
| Tags: | ibuf, ibuf, ibuf, ibuf, ibuf_mutex, ibuf_mutex, innodb, innodb, innodb, innodb | ||
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
[7 Jul 2010 18:44]
Alexey Stroganov
[3 Aug 2010 13:13]
Marko Mäkelä
Slightly reduce ibuf_mutex contention. Update the merge counters too.
Attachment: bug54914-2.patch (text/x-diff), 5.18 KiB.
[4 Aug 2010 18:55]
Marko Mäkelä
Same as above, and invoke ibuf_entry_build() before acquiring ibuf_mutex.
Attachment: bug54914-3.patch (text/x-diff), 7.15 KiB.
[9 Aug 2010 12:54]
Marko Mäkelä
Untested patch to reduce ibuf_mutex contention further. Perform some dirty reads on purpose.
Attachment: bug54914-4.patch (text/x-diff), 4.91 KiB.
