Note that there are some explanatory texts on larger screens.

plurals
  1. PODo InnoDB vs MyISAM comparisons still hold true in terms of speed of reads vs writes?
    primarykey
    data
    text
    <p>I know there are <a href="https://stackoverflow.com/questions/tagged/innodb+myisam">a bunch of other questions</a> on this. The problem I'm having is finding an <em>up to date</em> consensus on the matter with regards to the latest versions of the storage engines. </p> <p>Some people have said that for reads MyISAM is faster, but 'recent' improvements in InnoDB have either alleviated or eradicated this difference. Is that the case?</p> <p><a href="http://www.mysqlperformanceblog.com/2007/01/08/innodb-vs-myisam-vs-falcon-benchmarks-part-1/" rel="nofollow noreferrer">This article</a> at MYSQL Performance Blog gets linked to a lot, both directly and from other articles that have been linked to from questions on here, but it's 3 years old. We're developers, we practically work on dog years - 3 years is an AGE!</p> <p>--</p> <p>I have a number of tables, some of which are mostly written to and some of which are mostly read from and hardly ever written to. There's also a lot of foreign keys which require InnoDB anyway so those will stay as InnoDB, but I would like to know if I'm right to change the tables that are mostly read from and have no foreign keys to MyISAM, or whether this is a pointless thing to do, with the latest versions of the two storage engines being used?</p> <p>--</p> <p><em>I appreciate that this may be voted to be closed, but if doing so please you could link to an up to date article? I've already tried a Google search restricted by timeframe but the articles linked to the same older articles. Thanks.</em></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload