Bug #70641 5.6 partitions use much more memory than 5.1
Submitted: 16 Oct 2013 23:56 Modified: 29 Jul 2014 16:04
Reporter: Yoshinori Matsunobu (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Partitions Severity:S3 (Non-critical)
Version:5.6.14 OS:Any
Assigned to: CPU Architecture:Any

File: Maximum allowed size is 50MB.
Description:
Privacy:

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:

[27 Mar 2014 11:32] Mattias Jonsson
Profile from google perftools; heap profile for one db with 100 tables with 100 partitions each in mysql-5.1

Attachment: heapprofile.db2.100t100p.51.4.pdf (application/pdf, text), 12.70 KiB.

[27 Mar 2014 11:33] Mattias Jonsson
Profile from google perftools; heap profile for one db with 100 tables with 100 partitions each in mysql-5.5

Attachment: heapprofile.db2.100t100p.55.2.pdf (application/pdf, text), 11.16 KiB.

[27 Mar 2014 11:35] Mattias Jonsson
Profile from google perftools; heap profile for one db with 100 tables with 100 partitions each in mysql-5.6

Attachment: heapprofile.db2.100t100p.56.2.pdf (application/pdf, text), 11.62 KiB.

[27 Mar 2014 11:37] Mattias Jonsson
mysql-5.6 with ha_innobase::srch_key_val allocated in index_init() and freed in index_end()

Attachment: heapprofile.db2.100t100p.56.4.pdf (application/pdf, text), 13.29 KiB.

[30 Jul 2014 12:34] Mattias Jonsson
Patch for mysql-5.6.19

Attachment: bug70641-5.6.19.diff (application/octet-stream, text), 12.12 KiB.