I have a database with about 30 tables and 5 tables of them is write-intensive.
I'm considering
Convert 5 write-intensive tables to use InnoDB engine and keep the rest on MyISAM engine
Convert all tables to use InnoDB engine.
I wonder which approach is better?
To be more specific
The reason I want to keep some table on MyISAM engine is some of them has around 1,000,000 rows. I'm not sure how slower it will be for queries like "SELECT COUNT(*)" on these tables after converted to InnoDB.
I haven't done a test. I prefer getting some advices from any of you before start the switch.
These days, I always default to using InnoDB, especially on the write-intensive tables you mention where MyISAM suffers from full table locking. Here's a to-the-point comparison.
Reasons to use MyISAM:
Reasons to use InnoDB:
The above was taken from this site , which no longer seems to be working.
pros and cons for each.
for (1) pros: less disk space usage, myisam much faster for read-heavy access patterns
cons: memory must be shared between the innodb buffers and myisam key buffers. innodb tables are about 4x bigger than their myisam counterparts. programmatic code must be adapted for deadlock handling.
just remember innodb will also lock if you're changing an indexed column or primary key.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.