| Bug #36600 | SHOW STATUS takes a lot of CPU in buf_get_latched_pages_number | ||
|---|---|---|---|
| Submitted: | 8 May 2008 17:20 | Modified: | 18 Jun 2010 22:55 |
| Reporter: | Mark Callaghan | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
| Version: | 5.0, 5.1 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | innodb, performance, show, STATUS | ||
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
[19 May 2008 15:40]
Vasil Dimov
[25 Sep 2009 14:48]
Anh Nguyen
'show innodb status' output
Attachment: status.out (application/octet-stream, text), 127.85 KiB.
