MyISAM和InnoDB [英] MyISAM versus InnoDB

问题描述

我正在处理涉及大量数据库写入的项目，我会说（ 70％插入和30％读取）。这个比率还将包括我认为是一次读取和一次写入的更新。读取可能是脏的（例如，我不需要在读取时的100％准确的信息）。

有问题的任务将做一个小时超过100万数据库事务。

I'm working on a projects which involves a lot of database writes, I'd say (70% inserts and 30% reads). This ratio would also include updates which I consider to be one read and one write. The reads can be dirty (e.g. I don't need 100% accurate information at the time of read).
The task in question will be doing over 1 million database transactions an hour.

我在网络上阅读了一堆关于MyISAM和InnoDB之间的差异的东西，而MyISAM似乎是我对特定数据库/表的明显选择我将使用这个任务。从我看来，正在阅读，InnoDB是好的，如果事务需要，因为行级锁定是支持。

I've read a bunch of stuff on the web about the differences between MyISAM and InnoDB, and MyISAM seems like the obvious choice to me for the particular database/tables that I'll be using for this task. From what I seem to be reading, InnoDB is good if transactions are needed since row level locking is supported.

任何人都有任何经验与这种类型的负载）？是MyISAM的方式吗？

Does anybody have any experience with this type of load (or higher)? Is MyISAM the way to go?

推荐答案

我通过表简要讨论这个问题，所以你可以得出结论， InnoDB 或 MyISAM 。
http://developer99.blogspot.com/2011/07/mysql- innodb-vs-myisam.html

I have briefly discuss this matter by table so you can conclude which has to be chosen either InnoDB or MyISAM. http://developer99.blogspot.com/2011/07/mysql-innodb-vs-myisam.html

以下是您应该使用哪种类型的小型概述：

Here is a small overview of which type you should use in which situation:

                                                 MyISAM   InnoDB
----------------------------------------------------------------
Required full-text search                        Yes      5.6.4
----------------------------------------------------------------
Require transactions                                      Yes
----------------------------------------------------------------
Frequent select queries                          Yes      
----------------------------------------------------------------
Frequent insert, update, delete                           Yes
----------------------------------------------------------------
Row locking (multi processing on single table)            Yes
----------------------------------------------------------------
Relational base design                                    Yes

总结：

Frequent reading, almost no writing   => MyISAM
Full-text search in MySQL <= 5.5      => MyISAM

在所有其他情况下， InnoDB 通常是最好的方法。

In all other circumstances, InnoDB is usually the best way to go.

这篇关于MyISAM和InnoDB的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！