CODEWITHSUNDEEP
mysqlinnodbmyisamstorage-engines
Jelle De Loecker
Jelle De Loecker

Reputation: 21985

MyISAM or InnoDB for a mostly-write table

I've got a table that receives around 50 inserts per second. Right now there are 700k records, using 160 MiB. My little VPS with 1 gig of ram is keeping up, but just barely.

I chose for InnoDB, as people say "it scales better", gets corrupt less frequently and implements row locking instead of table locking.

But is it the right choice for this?

I've also read MyISAM supports delayed inserts, which could be very interesting. (I wonder what the trade-off is with table locking)

Upvotes: 2

Views: 283

Answers (1)

Johan
Johan

Reputation: 76753

InnoDB, no question.

  • Row level locking
  • transactions
  • better integritry

InnoDB allows delayed inserts as well.

The only issue I can think off is that running MySQL without InnoDB support (special compile of the source) can use 100MB less memory.
Don't do that though, it's not worth the headaches.

Upvotes: 5

Related Questions