MyISAM partial conversion

[Luis Manson]

Im courently looking for optimizations to mysql, im between moving to MariaDB and keep MyISAM or moving to innoDB some tables

Right now i have the next tables to InnoDB:
gaadmin_login_logs, gaerror_logs, gasearch_keywords, gasearch_visitors

gasessions(MEMORY)

i wonder if moving the members table would make any difference, or any other table. I dont feel confident on moving the posts table yet

[yacenty]

I moved users and gallery images.
Performance is visible better. Previously we have had a lot of LOCKS on members and pictures. Now those disapeard.
Somebody told me that InnoDB is slower. We have founded some benchmarks showing that read is slower on InnoDB, but when we have a huge ammount of UPDATEs and INSERTs, it's much efficient to have this table as InnoDB, because lock is on certain ROW not on whole TABLE

[yacenty]

on the other hand we had moved to the Percona DB - it was a huge performance boost.
Admin told me many queries were done 50% faster

[raindog308]

InnoDB excels at high-contention situations. It's slower than myisam for some things, faster for others.

Percona originally made their name as a Mysql clone with a better InnoDB.

[Luis Manson]

I knew about Percona, but since most of my tables still MyISAM I was thinking on MariaDB...
yacenty, you just converted the members table and nothinf else, right?

[yacenty]

yes, you are right

[Luis Manson]

thanks, i will give that a try, now i just need to understand if mysqloptimize will be whorst or what :S