Hi, we are looking for some feedback on developing more performance tuning snippets. Please try this out: http://drupal.org/node/50291 This should work in a MySQL 4.0 and 4.1 environment. I got a chance to spend some time with Brian Aker, the head of architecture for MySQL, again today. He suggested we use InnoDB for large sites and that we investigate using Archive table types which are designed specifically for tables like accesslog in Drupal. Apparently they had some significant performance improvements at Yahoo, LiveJournal, and Slashdot. Cheers, Kieran
Kind of off-topic, but this reminded me of something...
He suggested we use InnoDB for large sites
Is there a particular reason that Drupal's database.mysql file hard-codes tables to use MyISAM rather than leaving this specification off so it just inherits whatever the default table type is? I found this thread http://drupal.org/node/43336 which makes reference to a development discussion on engine agnosticity (I'm pretty sure I just made that word up) but I wasn't able to find the original discussion. On the off-chance there isn't, here is a patch: http://drupal.org/node/50669
You mean this message? http://lists.drupal.org/pipermail/development/2005-December/012563.html and http://lists.drupal.org/pipermail/development/2005-December/012568.html On 2/22/06, Angie Byron <drupal-devel@webchick.net> wrote:
Kind of off-topic, but this reminded me of something...
He suggested we use InnoDB for large sites
Is there a particular reason that Drupal's database.mysql file hard-codes tables to use MyISAM rather than leaving this specification off so it just inherits whatever the default table type is? I found this thread http://drupal.org/node/43336 which makes reference to a development discussion on engine agnosticity (I'm pretty sure I just made that word up) but I wasn't able to find the original discussion.
On the off-chance there isn't, here is a patch:
participants (3)
-
Angie Byron -
Khalid B -
Kieran Lal