L
L
link002015-05-21 21:37:51
MySQL
link00, 2015-05-21 21:37:51

MyISAM and InnoDB - What is faster for reading and what for writing?

At least in theory / based on experience / benchmarks. Or does it depend on a whole bunch of nuances?

Answer the question

In order to leave comments, you need to log in

3 answer(s)
A
Andrey Slashchinin, 2015-05-22
@link00

The engines are completely different and you need to use them in different situations.
To choose, you need to at least determine what will be more?
MyISAM locks the entire table when data is changed, while any SELECT will wait for the operation to be completed. InnodDB uses the line lock method.
Those. if there are more inserts, then InnodDB wins due to row locking (google InnoDB MVCC) if there are more fetches, then MyISAM can use the query cache and there will be a noticeable gain.
This is only part of the nuances, you should also remember about the settings of MySQL itself.

F
Fortop, 2015-05-21
@Fortop

It all depends on the nuances.
If there is only one client, and in earlier versions, then reading / writing is faster in MyISAM
If there are many clients writing, then InnoDB is faster

S
Sergey, 2015-05-21
Protko @Fesor

postgresql
But seriously, then:
Something like that.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question