开发者

MyISAM or InnoDB for a mostly-write table

开发者 https://www.devze.com 2023-03-15 11:23 出处:网络
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'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'v开发者_StackOverflow社区e also read MyISAM supports delayed inserts, which could be very interesting. (I wonder what the trade-off is with table locking)


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.

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号