| Bug #102238 | log_writer uses too much CPU on small servers | ||
|---|---|---|---|
| Submitted: | 12 Jan 2021 20:35 | Modified: | 21 Dec 2023 8:49 |
| Reporter: | Mark Callaghan | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S5 (Performance) |
| Version: | 8.0.22 | OS: | Any |
| 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
[12 Jan 2021 20:39]
Mark Callaghan
[12 Jan 2021 20:40]
Mark Callaghan
Flamegraph from 5.7.31 that doesn't have CPU problems from log writer
Attachment: sb.perf.data.insert.range100.pk1.Jan10.224916.perf.scr.svg (image/svg+xml, text), 270.28 KiB.
