InnoDB Vs. MyISAM

[wdroush]

So I'm considering to move to InnoDB due to the amount of table locking I'm getting right now, which is about 1:2000, software says I may want to selectively use InnoDB on my database. I'm having the feeling that the calls and leads table are probably the hardest hit with updates.


What are the disadvantages to moving to InnoDB on a handful of high-use tables? Will I really see a performance improvement or is it just 20 minutes down and no real need unless we're looking at like a 2GB+ database?

1:2000 isn't bad, but I'm thinking future wise as the system grows.

I've also just increased my table_open_cache by 5x, it was only getting a 15% hit rate. See if that helps the lock rate.

[kbrill]

I use http://blog.mysqltuner.com/ to tune my databases, it works very well until you start to get terribly large tables, then a DBA becomes useful.

As for the benefits of INNDB over myISAM it really all depends on who you talk to, there are strong cases on both sides. I always send people here (http://www.mysqlperformanceblog.com/...sam-to-innodb/) first. Many, many points made all in one place. Personally for small DBs I stick with myISAM and only after the first gig would I consider going to INNODB and even then I would pay an expert to do it as it will require a retuning of your system.