Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

My new Wordpress database all the Wordpress created tables use InnoDB engine and plugin created table use MyISAM. But older site database all the tables use MyISAM table engine. I use MySQL 5.5.35-cll i686.

If I use two different table engines in a same database, it will reduce my site performance or are there any downside?

share|improve this question
    
What's the MySQL version? –  SparKot ॐ Feb 16 at 23:39
    
The downside is that some of your tables are still in MyISAM. –  Bill Karwin Feb 17 at 4:10
    
@ Sparkot, i have update the post. –  chris Feb 17 at 15:34
    
@ Bill, Thanks bill. You mean it's better go for InnoDB? –  chris Feb 17 at 16:10
1  
Yes, InnoDB supports ACID, data recovery, transactions, foreign keys, row-level locking -- none of which are supported by MyISAM. Also in modern versions of MySQL, InnoDB is faster and more scalable than MyISAM under most typical scenarios. –  Bill Karwin Feb 18 at 1:54

1 Answer 1

up vote 2 down vote accepted

Having InnoDB won't make MyISAM slower and vice versa. However you have to be more careful in memory allocation for InnoDB and MyISAM. Because they store data and indexes in different buffers. MyISAM:

  • Indexes in the key buffer
  • Data in file system cache

InnoDB:

  • Data and indexes (well, in InnoDB everything is indexes) in the buffer pool

So if you allocate more than necessary to InnoDB then MyISAM will have to access disk more often (and vice versa)

share|improve this answer
    
Thanks akuzminsky. So is it wise idea to convert rest of the tables to InnoDB engine? –  chris Feb 17 at 15:31
    
Unless there is a very good reason for MyISAM (e.g. need for full text indexes etc) I tend to recommend InnoDB. It's been very actively developing and at the moment is much better than MyISAM from point of view of reliability, performance, flexibility in tuning. Even from data recovery standpoint(yes, unfortunately that happens too) chance to get your data back is way too bigger with InooDB than with MyISAM –  akuzminsky Feb 17 at 15:58
    
Again thanks akuzminsky. I saw that some plugins display InnoDB fragmented. But when i try to optimize that table it's not success. Is it a normal? –  chris Feb 17 at 16:05
    
well, I'm not sure what plugins you mean. I know you can check InnoDB tablespace fragmentation with XtraBackup (percona.com/doc/percona-xtrabackup/2.1/xtrabackup_bin/…) . And yes, OPTIMIZE TABLE will rebuild a table, thus will defragment it. Not sure why it fails though. –  akuzminsky Feb 17 at 16:21
    
I use wpxtram. I think it's better contact the developer. Again thank you so much. –  chris Feb 17 at 16:32

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.