Geek Answers Handbook

Is InnoDb better for frequent simultaneous updates and inserts than MyISAM?

We have sites with hundreds of visitors every day and tens of thousands of queries per day. Thus, some tables in the database are updated very rarely, some tables are updated several times per minute, and some tables are updated ~ 10 times per second.
MyISAM uses table-level locking for updates, and InnoDb uses row-level locking.
So, as I understand it, for tables with frequent concurrent updates (several updates per second) it is better to make them InnoDb and for other tables (if we do not need transactions and foreign keys, of course) it’s ok to work with the MyISAM engine.
Am I right in my thoughts?

+2
source share
2 answers

MyISAM is faster to read and write, but not at the same time. In other words, if you need to write a lot, it will be faster, but if you want people to read at the same time, readers and writers will block each other, and you may have problems with concurrency. You should use InnoDB in such scenarios, and most mysql gurus recommend using InnoDB by default, as it is considered more reliable than MyISAM, although it is slower in some use cases.

+6
source

, . MySQL, , , innoDB , , MyISAM /DW.

0

More articles:


All Articles