I've a (large?) FreeRadius database with MySQL 5.0.51. When the database was set up, MyISAM engine was used. Since now we're experiencing some performance problems, I was considering the migration to InnoDB, which I read should be faster.
MySQL is a master/master replica setup. Since the ALTER TABLE will take some minutes (I did a test run on a separate db), and one of the two database while still active is not publicly accessible, I tought I could run the alter on the "offline" db first using the following: SET SQL_LOG_BIN=0; ALTER TABLE ... ENGINE=InnoDB; SET SQL_LOG_BIN=1;
then switch the online db and run the same on the second node. From what I've read around, and basicly here [1], the main adivces are about disk storage, but not much more...
My questions are: * will I really gain in performance by switching to Innodb? * is the above procedure a good schedule? * is there anything else I should care about, before starting?
Thanks! maxxer
[1] http://dev.mysql.com/doc/refman/5.0/en/converting-tables-to-innodb.html -- Lorenzo Milesi - lorenzo.milesi@yetopen.it
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
Nov 05
Rick James RE: Change storage engine to InnoDB
Nov 05, 2012; 15:59
Rick James
RE: Change storage engine to InnoDB
Nov 06
Lorenzo Milesi Re: Change storage engine to InnoDB
Nov 06, 2012; 10:55
Lorenzo Milesi
Re: Change storage engine to InnoDB
Nov 20
Lorenzo Milesi Re: Change storage engine to InnoDB
Nov 20, 2012; 16:09
Lorenzo Milesi
Re: Change storage engine to InnoDB
Nov 20
Rick James RE: Change storage engine to InnoDB
Nov 20, 2012; 21:37
Rick James
RE: Change storage engine to InnoDB
Nov 21
Lorenzo Milesi Re: Change storage engine to InnoDB
Nov 21, 2012; 09:25
Lorenzo Milesi
Re: Change storage engine to InnoDB
Search
Lasso Programming
This site manages and broadcasts several email lists pertaining to Lasso Programming and technologies related and used by Lasso developers. Sign up today!