0

I have 24GB RAM i7 dedicated server, running CPanel 11.36 with MySQL 5.1.68. In my.cnf I have innodb_file_per_table enabled. Is it safe to just disable the option, not doing any damage to databases in the meantime after MySQL restarts?

Improve this question
1
  • Can you paste in your my.cnf file? InnoDB performance can be dramatically altered based on settings in here. Also, are you using the built-in InnoDB or the InnoDB plugin?
    – user143703
    Jun 3, 2013 at 19:32

2 Answers 2

Reset to default
3

Disabling innodb_file_per_table affects only newly created tables, so it is safe to turn it off or on at any time. Why do you want to turn it off?

Improve this answer
3
  • I am having performance issues with the server (caused by MYSQL) and I can't pinpoint the cause. I have the impression that enabled innodb_file_per_table is more CPU intensive. The server has only 6 low-traffic websites, but one of them (a Joomla 3.1 200MB db site) seems to have enormous impact on the box. I am trying various configurations.
    – axinos
    Jun 3, 2013 at 14:10
  • 1
    I don't think that innodb_file_per_table is the cause for your performance issue. Nevertheless you can give it a try. Can you identify a bad performing query?
    – Pascal Schmiel
    Jun 3, 2013 at 14:20
  • I have enabled slow query log but I have no record (yet).
    – axinos
    Jun 3, 2013 at 15:26
3

Disabling the option is fine. What will happen is any new tables agoing forward will be created in the shared tablespace instead of in it's own file.

However, there is almost no good reason to disable this option. Having the tables in their own file gives you lots of good with almost zero bad. By switching the feature off, you loose all of that good.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .