Some of the parameters changed in MySQL 5.6, however we use the same configuration as for MySQL 5.5. I would suggest creating my.cnf-5.6. max_allowed_packet = 1M (5.6 default is 4MB) table_open_cache = 64 (5.6 default 2000) net_buffer_length = 8K (5.6 default 16KB) innodb_buffer_pool_size = 16M (5.6 default 128MB) innodb_additional_mem_pool_size = 2M (As of MySQL 5.6.3, innodb_additional_mem_pool_size is deprecated and will be removed in a future MySQL release) innodb_log_file_size = 5M (5.6 default 48MB)
(In reply to Tomas Mozes from comment #0) > innodb_log_file_size = 5M (5.6 default 48MB) This one is a little difficult to change automatically. It requires a user to delete the old ib_logfile{0,1} files or the server will refuse to start. It really should be done by the admin. I will look at the others.
Seems like in 5.6 it's not that complicated anymore. I tried resing from 5MB to default 48MB. 2014-10-08 16:12:27 6171 [Warning] InnoDB: Resizing redo log from 2*320 to 2*3072 pages, LSN=20221136 2014-10-08 16:12:27 6171 [Warning] InnoDB: Starting to delete and rewrite log files. 2014-10-08 16:12:27 6171 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB 2014-10-08 16:12:27 6171 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB 2014-10-08 16:12:28 6171 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0 2014-10-08 16:12:28 6171 [Warning] InnoDB: New log files created, LSN=20221136 See also: http://www.percona.com/blog/2013/09/05/my-favorite-secret-mysql-5-6-feature/
Done. Thanks for the pointers. Though I did limit table_open_cache to 400 for now (5.5 default but still greatly improved). I may revisit this after testing how the default ulimit of 1024 would be affected or any issues from it.
