Only thing I thought we will loose when switching from MyISAM to InnoDB was awesome Yet Another Related Posts Plugins.
But while surfing YARPP plugin’s support forum, I got to know it works nicely with InnoDB also. It shows a warning, which can be ignored.
Once you ignore the warning, you need to tweak your relatedness settings with categories and tags.
Relatedness options
Please note that you can not use title and bodies. They require FULLTEXT search. MySQL 5.6 supports FULLTEXT index for InnoDB engine but YARPP plugin is not updated for this new MySQL 5.6 addition.
I tried reaching Mitcho but did not get any response. So for now, we are using YARPP with less relevant match but its still better than nothing!
InnoDB is more important that relatedness accuracy
This WordPress setup has a blog post, products’ documentation (500+ pages), bbPress forum, woocommerce, our own WordPress-based CRM and some more functionality. All of these uses WordPress posts and postmeta table. So MyISAM tables were slowing down a lot because MyISAM do not support row-level locking.
We are getting faster page-loading for logged in users since we moved to InnoDB! Its fast enough to sacrifice relatedness accuracy.