tag:blogger.com,1999:blog-2361800974999510068.post7646778526814360174..comments2023-10-21T05:09:51.935-07:00Comments on Simple life, Complicated mind: InnoDB COUNT(id) - Why so slow?Jun Hsiehhttp://www.blogger.com/profile/00640061359079216681noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-2361800974999510068.post-45825539596742896482010-03-12T12:51:37.778-08:002010-03-12T12:51:37.778-08:00found another time you might want to consider inno...found another time you might want to consider innodb for its record level locks. I have a fairly big DB that gets mostly read from. If all you're doing is a bunch of reads... myisam is great. But as soon as you updates or inserts... you're dealing with table level locking. So if you have someone grabbing a long-ish query (for example: getting a copy of all the records), and then some updates get queued up to be executed... you can run into a lock situation where the big select query has frozen your entire server until it completes because those updates aren't eligible to run until after the select is done. That's very very bad.ScWhttp://devpicayune.comnoreply@blogger.com