<br><br><div class="gmail_quote">On Nov 26, 2007 4:41 PM, Earnie Boyd <<a href="mailto:earnie@users.sourceforge.net">earnie@users.sourceforge.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Quoting Khalid Baheyeldin <<a href="mailto:kb@2bits.com">kb@2bits.com</a>>:<br><br>> - Add skip-innodb, which saves some 100MB of RAM for the MySQL.<br>><br><br></div>Speaking of innodb; I've been testing with it as well. InnoDB can be
<br>slightly faster with selects that MyISAM and provides for row locking<br>which you can't do with MyISAM.<br></blockquote></div><br>With some pitfalls.<br><br>When you do a SELECT COUNT(*) FROM ... it is very slow on InnoDB.
<br>MyISAM just consults the index and gets you the number instantly. On <br>InnoDB, the index is co-resident with the data, not separate, hence it <br>is slow.<br><br>So, most of the queries in Drupal that need to know the number of rows
<br>and do SELECT COUNT(*) are slower. For example pager_query() stuff.<br clear="all"><br>Also, explicit table locking is gone in Drupal 6 (at least for core), so both <br>MyISAM and InnoDB will (should?) benefit from that.
<br>-- <br>Khalid M. Baheyeldin<br><a href="http://2bits.com">2bits.com</a><br><a href="http://2bits.com">http://2bits.com</a><br>Drupal optimization, development, customization and consulting.