Debería mover a InnoDB durante una migración planificada?

Question

Estoy en breve la migración de un servidor web de Debian Lenny a otro anfitrión y Debian Squeeze. La instalación de MySQL estándar incluso en Squeeze es de 5.1 y por lo tanto sería por defecto a MyISAM - me siento inclinado a seguir con mi regla de oro que siempre me quedo con un estándar de Debian instalar como sea posible para obtener la máxima estabilidad, especialmente en lo que permite InnoDB no lo hace parecen ser completamente a toda prueba

La carga de transacciones en la base de datos es mínimo, ya que es un sitio web con poco tráfico. Estoy más preocupado con el mantenimiento de la gestión de lo más simple posible que cualquier otra cosa. El sitio cuenta con una versión personalizada de WordPress desarrollado por una tercera parte.

Debo añadir que mi experiencia con MySQL en cualquier forma es mínima.

En caso me quedo con mi plan o tomar la oportunidad de ver en InnoDB?

Answer 1

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

Answer 2

This is just chime-in on @DTest's answer.

I agree with his answer concerning pros and cons of Migration From MyISAM to InnoDB

I would like add that setting up caching for MyISAM is more simplistic that InnoDB because you have to worry about InnoDB log files in conjunction with the buffer pool usage and sizing objects that can be stored in it. MyISAM is just setting up enough cache for MYI index pages.

Since your site is already low traffic, you should remain as you are in MyISAM, provided that there will be no expected rise in traffic in the immediate future.

So as not to steal anyone's thunder, @DTest's answer hits the nail right on the head as per MyISAM pros and cons. Additionally, InnoDB will provide too much firepower for a low traffic website (needless overkill).