Bug #67259 | MySQL 5.5.x uses more memory than 5.1.x when temporary tables are used | ||
---|---|---|---|
Submitted: | 16 Oct 2012 10:21 | Modified: | 8 Jul 2013 12:08 |
Reporter: | Valeriy Kravchuk | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: DML | Severity: | S2 (Serious) |
Version: | 5.5.27, 5.5.28 | OS: | Linux ( 2.6.35.14-106.fc14.x86_64) |
Assigned to: | CPU Architecture: | Any | |
Tags: | regression |
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 Oct 2012 12:33]
Ovais Tariq
[20 Oct 2012 8:06]
Ovais Tariq
Log of memory usage generated by my test script, but with tmp_table_size set to 10M
Attachment: memory_usage_10M_tmp_tbl_size.log (application/octet-stream, text), 2.69 KiB.
[20 Oct 2012 10:32]
Ovais Tariq
Memory usage by implicit in-memory tmp tables on MySQL 5.5.23
Attachment: mysql_5523_mem_usage_256M_tmp_tbl_size.log (application/octet-stream, text), 4.62 KiB.
[20 Oct 2012 10:33]
Ovais Tariq
Memory usage by in-memory implicit tmp tables in MySQL 5.5.28
Attachment: mysql_5528_mem_usage_256M_tmp_tbl_size.log (application/octet-stream, text), 4.58 KiB.
[21 May 2013 7:49]
Jervin R
Massif output from 5.5.30
Attachment: issue-30580-valgrind-massif-5.5.30.out (application/octet-stream, text), 555.72 KiB.
[21 May 2013 7:50]
Jervin R
Massif output from 5.5.31
Attachment: issue-30580-valgrind-massif-5.5.31.out (application/octet-stream, text), 674.45 KiB.