Jump to content

InnoDB vs myISAM

From tango.info wiki

http://stackoverflow.com/questions/1381186/fulltext-search-with-innodb

phpMyAdmin uses a quick method to get the row count, and this 
method only  returns an approximate count in the case of InnoDB tables. 
See $cfg['MaxExactCount'] for a way to modify those results, 
but this could have a serious impact on performance.
If you want fast, MyISAM style, just set 
innodb-flush-log-at-trx-commit=2
and you get InnoDB fast too (with some risk of data loss, 
just like in MyISAM)
...
...problem with innodb-flush-log-at-trx-commit=2 is that it is global.
"select count(*) from my_table;" MyISAM knows the answer 
to this instantly whereas InnoDB may take a minute or 
more to make up its mind.
MyISAM scales better with very large datasets. InnoDB outperforms 
MyISAM in many situations until it can't keep the indexes in memory, 
then performance drop drastically.
...
You can copy the DB files associated with a MyISAM table to another
computer and just put them in the MySQL data directory and MySQL will
automatically add them to the available tables.