Should I move to InnoDB during a planned migration?

I'm shortly migrating a Debian Lenny webserver to another host and Debian Squeeze. The standard MySQL installation even on Squeeze is 5.1 and therefore would default to MyISAM - I'm inclined to stick with my usual rule of thumb that I stay with as standard a Debian install as possible for maximum stability, particularly as enabling InnoDB doesn't seem to be completely fool-proof

The transactional load on the database is minimal as it is a low traffic website. I'm more concerned with keeping management as simple as possible than anything else. The site runs a customised version of WordPress developed by a 3rd party.

I should add that my experience with MySQL in any form is minimal.

Should I stick with my plan or take the opportunity to look into InnoDB?

To be honest, with a low traffic environment running on 5.1, you shouldn't have any problems with MyISAM. The biggest downfall of MyISAM is table-locking WRITES, IMO. But with limited data in the tables, this won't be noticeable.

MyISAM is probably easier to manage from a DBA standpoint with recovery and repair.

And in 5.1, I think InnoDB's benchmarks aren't really up to par. I could be wrong on this, so I'm going to look it up again!

Edit: Quick google turned up this article in 2009 using 5.1 http://www.mysqlperformanceblog.com/2009/01/12/should-you-move-from-myisam-to-innodb/

Gives some nice talking points, specifically the section on InnoDB needing tuning.

HTH

StackExchange Database Administrators Q#2885, answer score: 6