| Bug #13578 | The longer mysqld runs, the slower everything is | ||
|---|---|---|---|
| Submitted: | 28 Sep 2005 17:10 | Modified: | 4 Sep 2006 7:08 |
| Reporter: | Shawn Hogan | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 5.0.21, 4.1.18 | OS: | MacOS (Mac OS X Server 10.4.4) |
| 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
[28 Sep 2005 17:11]
Shawn Hogan
[28 Sep 2005 17:12]
Shawn Hogan
Output of SHOW STATUS and SHOW VARIABLES immediately before a needed restart
Attachment: mysql_probs.txt (text/plain), 29.08 KiB.
[6 Oct 2005 15:18]
Shawn Hogan
Shows almost every mysqld thread hung on opening/closing files
Attachment: processlist1.txt (text/plain), 154.10 KiB.
[6 Oct 2005 15:19]
Shawn Hogan
All query threads with a NULL state
Attachment: processlist2.txt (text/plain), 148.22 KiB.
[6 Oct 2005 15:21]
Shawn Hogan
No state on any query thread except for one that's doing an INSERT into a tiny HEAP table
Attachment: processlist3.txt (text/plain), 23.46 KiB.
