# my.cnf wizard

**URL:** <https://forums.percona.com/t/my-cnf-wizard/3672>\
**Category:** LAMP Stack\
**Created:** [August 11, 2014, 8:26am UTC](https://forums.percona.com/t/my-cnf-wizard/3672 "2014-08-11T08:26:40Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![MTremb](https://avatars.discourse-cdn.com/v4/letter/m/54ee81/32.png) [@MTremb](https://forums.percona.com/u/MTremb)\
**Post date:** [August 11, 2014, 8:26am UTC](https://forums.percona.com/t/my-cnf-wizard/3672/1 "2014-08-11T08:26:40Z")

</div>

Hello,

I used your my.cnf wizard to optimize mysql on a domU xen server. The server is running centos 6.5. After copying and pasting the result into my.cnf, I couldn’t restart mysql and was obliged to return to the default my.cnf.

cat /var/lib/mysql/mysql-error.log

140810 21:21:00 mysqld\_safe Starting mysqld daemon with databases from /var/lib/mysql/  
140810 21:21:00 InnoDB: Initializing buffer pool, size = 128.0M  
140810 21:21:00 InnoDB: Completed initialization of buffer pool  
InnoDB: Error: log file ./ib\_logfile0 is of different size 0 5242880 bytes  
InnoDB: than specified in the .cnf file 0 67108864 bytes!  
140810 21:21:00 [ERROR] Plugin ‘InnoDB’ init function returned error.  
140810 21:21:00 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.  
140810 21:21:00 [ERROR] Unknown/unsupported table type: InnoDB  
140810 21:21:00 [ERROR] Aborting

140810 21:21:00 [Note] /usr/libexec/mysqld: Shutdown complete

140810 21:21:00 mysqld\_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

Please advise

---

<div class="post-metadata">

**Author:** ![scott.nemes](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/scott.nemes/32/5_2.png) [@scott.nemes](https://forums.percona.com/u/scott.nemes)\
**Post date:** [August 12, 2014, 9:54am UTC](https://forums.percona.com/t/my-cnf-wizard/3672/2 "2014-08-12T09:54:05Z")

</div>

The issue is that the new config has a larger value for your ib\_logfile sizes (innodb\_log\_file\_size). Move your current ib\_logfiles to another location for safe keeping (you can delete them, but if you want to be extra careful you can just move them instead). MySQL will then recreate new ib\_logfiles of the new size when you start up MySQL again.

---

<div class="post-metadata">

**Author:** ![MTremb](https://avatars.discourse-cdn.com/v4/letter/m/54ee81/32.png) [@MTremb](https://forums.percona.com/u/MTremb)\
**Post date:** [August 13, 2014, 12:31pm UTC](https://forums.percona.com/t/my-cnf-wizard/3672/3 "2014-08-13T12:31:54Z")

</div>

Thanks. On a separate note, I have several databases running on the server. Some are using innodb and one is using myisam. As the wizard’s config optimizes innodb, I’m wondering if it would have a negative effect on the performance of the myisam database.

---

<div class="post-metadata">

**Author:** ![scott.nemes](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/scott.nemes/32/5_2.png) [@scott.nemes](https://forums.percona.com/u/scott.nemes)\
**Post date:** [August 13, 2014, 12:56pm UTC](https://forums.percona.com/t/my-cnf-wizard/3672/4 "2014-08-13T12:56:28Z")

</div>

It’s definitely possible that it could cause performance to degrade for the MyISAM portion. The tool gives you a generic “best practice” my.cnf to start with that may work for most people, but what you actually need could be very different depending on your setup (especially if you heavily use both InnoDB and MyISAM).

The most critical setting for MyISAM is generally key\_buffer\_size, so if you do notice an issue you could try upping that setting and lowering the innodb\_buffer\_pool\_size to account for it (otherwise you’ll end up with memory problems).

This is why benchmarking is important, so you know exactly what the performance is before and after, and can make adjustments as needed. =)