There is a default my.cnf on your dedicated server that comes with MySQL (4+5) that will make MySQL run a bit quicker if you have 2+ gig of ram
cp -f /usr/share/mysql/my-large.cnf /etc/my.cnf
NOTE 1 the log-bin option is enabled by default. This will quickly use a lot of disk space. It’s recommended to comment out the log-bin line from your /etc/my.cnf
, if it exists.
NOTE 2 Take note of your old /etc/my.cnf
file. If you have innodb_file_per_table=1, make sure the new my.cnf
you install also has this setting. Similarly, if your old one does not have innodb_file_per_table=1 enabled, then your new my.cnf should also not have it enabled. If the new my.cnf
has a different setting for innodb_file_per_table, then it may corrupt your data.
Be sure to make full backups of your .sql files before doing any changes to your my.cnf.
We don’t currently have optimized my.cnf files for these OSs. The /etc/my.cnf
will rely on the internal defaults in the mysqld binaries.
If your MySQL data directory has many files such as:
mysql-bin.000001
mysql-bin.000002
...
log-bin=mysql-bin
The solution to prevent those files from being created is to comment out the log-bin option from the my.cnf by adding at # character at the start of the line (left side).
The internal default is “OFF”, hence removing it will disable it.
You can delete your mysql-bin.0* files after mysqld has been restarted. Read more