Comparison of InnoDB and MyISAM is still fair in terms of read and write speed?

Question

I know that there are a bunch of other questions . The problem I am facing is to find a modern consensus on the latest versions of storage engines.

Some people said that reading MyISAM is faster, but the “recent” improvements in InnoDB have either eased or eliminated this difference. Is this the case?

This MYSQL performance blog article is linked to a large number, both directly and with other articles that were related to the questions here, but he is 3 years old. We are developers, we practically work on the dog years - 3 years - this is AGE!

-

I have several tables, some of which are mostly written, and some of them are mostly read and almost never written. There are also many foreign keys that require InnoDB to remain InnoDB anyway, but I would like to know if I can change tables that are mostly readable and do not have foreign keys for MyISAM, or is this a pointless thing to do use using the latest versions of two storage systems?

-

I appreciate that it can be voted for closing, but if you do, please can you contact the updated article? I already tried Google search, limited by timeframe, but articles related to the same old articles. Thanks.

Answer 1

As you point out, the MySQL Performance Blog article has been around for almost 4 years. Since then, InnoDB has been greatly improved. MyISAM was not.

MySQL 5.5 was released just yesterday. This is the first version where InnoDB is the default storage engine. Because of. Oracle claims to achieve 3.5 times performance for Linux and up to 15 times better performance for Windows (compared to 5.1 InnoDB).

Answer 2

I would say there is almost no difference. I recently read an article that dispelled this myth, but Sadi doesn't seem to be working anymore.

Anyway, I really believe that the discrepancy between MyISAM and InnoDB now depends mainly on the issues

• Do you need to work with foreign keys?
• You need a table level or row level lock.

At least these are the principles on which I base my options.

Answer 3

In general, the consensus seems to be to use InnoDB first, but there are still some areas where MyIsam is much faster than InnoDB. I have a website listing times for Running Races and creating an entry for each athlete www.marastat.com . Our site has a million range athletes. We added a search function and searched by first and last name and found that using InnoDB and Index took more than a minute to complete some searches. We duplicated the InnoDB table and added full text indexes in the MyIsam version, and most queries can complete in a second or two.