Comments on: myisam and innodb storage explained http://www.yqed.com/mysql-storage-myisam-innodb-explained/ floren's random thoughts and segments of code Thu, 15 Dec 2011 10:35:01 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Floren http://www.yqed.com/mysql-storage-myisam-innodb-explained/comment-page-1/#comment-918 Floren Mon, 16 Nov 2009 18:40:30 +0000 http://www.yqed.com/?p=165#comment-918 Actually, continuing to use MyISAM does not affect anything related to performance, if you know what you are doing. InnoDB can create maintenance nightmares that ultimately increase the overall costs. I know several large sites that run on MyISAM with no issues. Losing your SELECT speed is not worth as a trade-in for row locks. Searchlight can help you to easily remove all your locks and decrease server costs substantially, with no switch to InnoDB. I will post detailed reports and graphics, when the beta period ends. Plus, whatever IBAnders describes in his blog is inaccurate. It has been tried before to make usage of InnoDB into optimizing search tables, without success. Currently, the new framework developed in vB4 is extremely complicated for its intended usage (way too much abstraction, for example) and that alone combined with inefficient coding techniques increases the server load significantly. Actually, continuing to use MyISAM does not affect anything related to performance, if you know what you are doing. InnoDB can create maintenance nightmares that ultimately increase the overall costs. I know several large sites that run on MyISAM with no issues. Losing your SELECT speed is not worth as a trade-in for row locks. Searchlight can help you to easily remove all your locks and decrease server costs substantially, with no switch to InnoDB. I will post detailed reports and graphics, when the beta period ends.

Plus, whatever IBAnders describes in his blog is inaccurate. It has been tried before to make usage of InnoDB into optimizing search tables, without success. Currently, the new framework developed in vB4 is extremely complicated for its intended usage (way too much abstraction, for example) and that alone combined with inefficient coding techniques increases the server load significantly.

]]> By: Chris D http://www.yqed.com/mysql-storage-myisam-innodb-explained/comment-page-1/#comment-917 Chris D Sun, 08 Nov 2009 04:56:19 +0000 http://www.yqed.com/?p=165#comment-917 IF you have noticed, vBulletin 4.0 is switching things over to innodb as posted by ibanders on the blog there. Is this cause for concerns for large forum owners looking at the future of their sites? IF you have noticed, vBulletin 4.0 is switching things over to innodb as posted by ibanders on the blog there.

Is this cause for concerns for large forum owners looking at the future of their sites?

]]>