If I'm optimizing a database that will be delivering multiple Drupal 7 websites, all using InnoDB, do I need to worry about [myisamchk] & [isamchk] sections, or can I just worry about the stuff within [mysqld]?

I'm assuming if I delete these sections, that the defaults will just kick in if they are needed.

I'm trying to document, outline my.conf best practices here http://groups.drupal.org/node/289613

1 Answer 1


The other group headers have no bearing on InnoDB whatsoever. [mysqld] is all you really need.

With regard to InnoDB itself, you will need to tune InnoDB in many aspects

System Tablespace / Individual Tablespaces

Buffer Pool

Transaction Logs

Multiple CPU / Multiple Core Engagament


There are so many other aspects I have no time to write about because I probably have written it already. Please see all my posts on InnoDB.

What is also worth noting is that you should be using the latest version of MySQL

On a side note, did you know the StackExchange has a Drupal Q&A site ? I have posted answers there as well.

  • Thanks RolandoMySQLDBA - this is a useful list. I wanted to post to the DBA list as I figured it would be a better place to get feedback like this. It's useful to get this direction. Mar 28, 2013 at 15:20
  • I'm not clear from the issue on innodb_file_per_table if it is needed as it seems to be defined that way by default. Also, it's unclear if innodb_file_per_table or innodb_file_per_table=1 are the same. Apr 3, 2013 at 18:47
  • Don't worry. Setting innodb_file_per_table or innodb_file_per_table=1 is synonymous. The default for innodb_file_per_table is 1 for MySQL 5.6 GA (dev.mysql.com/doc/refman/5.6/en/…) and 0 for MySQL 5.5 GA (dev.mysql.com/doc/refman/5.5/en/…) Apr 3, 2013 at 19:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.