What is wise? Innodb_file_per_table or not?

Richard G

Verified User
Joined
Jul 6, 2008
Messages
13,530
Location
Maastricht
Since we upgraded to mysql 5.5 we're using this as the my.cnf on the servers:

[mysqld]
local-infile=0
bind-address = 127.0.0.1
default-storage-engine=MyISAM
innodb_file_format=Barracuda
innodb_file_per_table=1
open_files_limit = 2048

This last line was added because of some "too many open file" errors which froze the mysql server. We did not have that issue on mysql 5.1 as far as I remember.
I got those settings from a post from Ditto on the DA forum.

But what worry's me is the innodb_file_per_table=1 setting since my knowledge of Mysql is fairly little.
When reading around I'm wondering if there are any benefits to this, because it seems that is only slows mysql down as can alo be read [url=http://umangg.blogspot.nl/2010/02/innodbfilepertable.html]here
.

So in fact I'm wondering if this is a good setup I'm using.

How do you setup your my.cnf by default?
 
Back
Top