Hi,
I'd like to request that the default my.cnf on new cPanel installations include "innodb_file_per_table=1". According to this thread, there is an internal feature request for this, but I'd like to make this a public request in order to gain support from the forums for the idea. I'd also like to expand upon the reasons why this is a good idea. The thread I linked says the feature request is case #41802, so I put that in the title here.
Expanded reason why innodb_file_per_table should be in the default my.cnf:
- innodb_file_per_table is required in order to use advanced file formats like Barracuda. See link for reasons one might like to do this: Real-Life Use Case for “Barracuda” InnoDB File Format - MySQL Performance Blog
- When innodb_file_per_table is not set, the shared table space can get very large, and reclaiming this space is extremely difficult. This page illustrates the complexity of reclaiming that space: Reclaiming Your InnoDB Tablespace — mysqlhacker
- Going from innodb_file_per_table back to the shared tablespace (should one be inclined) is much less problem-prone than the reverse.
- Unless you have several tens of thousands of tables with a heavy write load, the separate tablespace performs just as well as the shared tablespace. In some cases, the separate tablespace outperforms the shared space (see list item #1).
- innodb_file_per_table avoids this issue:
- Separate tablespaces suffer less fragmentation than the shared tablespace.
For the record, this request is only to apply to new cPanel installations.



LinkBack URL
About LinkBacks
Reply With Quote





