On Rackspace Cloud Server, Cloud Sites, Dedicated Server, OnMetal, usually Innodb is used. Innodb offers better performance on better hardware. First and most important point is that, I am not a database Guru. Only a true expert and a fool can say give opinion! MySQL is so much specialized and when it is about which MySQL Engine, honestly it is quite difficult for me to explain. As the question was asked by a reader of the website after reading the Optimizing MySQL Database Performance guide, I am trying to answer. First there is huge difference between what we write as guide and use – we use high end setup, it costs quite higher and we do not expect that a person who is seeking some free help can afford so much for running a small website or a website with huge un-targeted traffic with very low CPC. Obviously we use separate MySQL database setup on Rackspace Cloud Server, but that is also not one server.
MyISAM vs Innodb MySQL Engine For WordPress (Rackspace Cloud)
As we need a defined hardware to suggest about MySQL Engine For WordPress, Practically this is the typical MyISAM vs Innodb war; we have to tell about the provider that we are using for the last 5 years. That is Rackspace Cloud. That explains why we named the guide as MyISAM vs Innodb MySQL Engine For WordPress (Rackspace Cloud).
MyISAM vs Innodb MySQL Engine For WordPress – What Rackspace Cloud Officially Says
Rackspace tends towards Innodb :
Innodb MySQL Engine with 2 GB Server (PVHVM) with 2 virtual cores as database server with 5K+ posts works far better than MyISAM. You can read this analysis :
Atomicity, Consistency, Isolation, Durability (ACID) are the deciding factors. Most Plugins works great for Innodb MySQL Engine except Yet Another Related Posts Plugin (YARPP). This is a logically right plugin which can make a website slowest possible. With Innodb MySQL Engine it runs somehow now, but there is no compromise in speed. Do not convert InnoDB to MyISAM, this is possibly a worst idea!
MyISAM vs Innodb MySQL Engine For WordPress – How To Convert?
If you want to convert, only practical way to rightly convert MyISAM driven one to Innodb driven, is to export all the things as XML export – this is a database Engine independent method. There are SQL queries to convert, but what can happen with the plugins, it is difficult to say. With Ngnix PHP5-FPM, good CDN, Fragment Caching and Innodb MySQL Engine, no WordPress Cache plain is required. Allow WordPress to function as PHP is intended for.
Follow the Author of this article :