Geek Answers Handbook

When is the time to change the table from MyISAM to InnoDb?

This question is similar to the continuation of my previous question: Am I right that InnoDb is better for frequent simultaneous updates and inserts than MyISAM?

But this time I have specific questions.
We know that MyISAM is faster than InnoDb when we do not have many simultaneous updates (inserts). When we have many simultaneous updates, the MyISAM table is locked and all other clients must wait.

1) But when is the time to switch from MyISAM to InnoDb? 1 update every second? 10 updates every second? 100 updates every second?
2) For a specific example, is it better to change InnoDb to one of the tables on my website, where I usually have several updates per minute (from different sessions), but sometimes it can be ~ 2-3 updates per second?

+5
source share
2 answers

I think your questions were pretty much satisfied in the previous question you were talking about.

1) . InnoDB , . , sql, , /, .. (TPS) , InnoDB .

2) 2-3 TPS InnoDB MyISAM. - .

FYI, 200 .

InnoDB, MVCC ACID.

+3

, , .

. , innodb, myisam-workload. ( , ).

, 16G , , , 12G innodb, MyISAM.

, MyISAM, , , innodb (, 6G) myisam.

myisam-innodb .

, , .

, : " , MyISAM , InnoDb".

InnoDB , InnoDB MyISAM ( , , ).

, " ".

, innodb /, , - , MyISAM, , .

+1

More articles:


All Articles