Commanding Chaos for Coworking, Open Source and Creative Communities

Error message

  • Deprecated function: session_set_save_handler(): Providing individual callbacks instead of an object implementing SessionHandlerInterface is deprecated in drupal_session_initialize() (line 245 of includes/session.inc).
  • Deprecated function: Creation of dynamic property alpha_theme_container::$delta is deprecated in alpha_theme_container->__construct() (line 25 of sites/all/themes/contrib/omega/alpha/includes/base.inc).

MySQL Engines: MyISAM vs. InnoDB | Tag1 Consulting

Wed, 12/28/2011 - 10:37 -- rprice

In most cases, InnoDB is the correct choice for a Drupal site. It provides increased concurrency, enhanced performance and much more data integrity than MyISAM ever can. However, the pluggable nature of MySQL engines allows the user to "mix and match" table engines inside a single database. This allows us to consider tables whose workloads fit MyISAM more so than InnoDB. The main candidates for MyISAM in a mostly InnoDB-centric database are the search tables. A database layout with most tables being InnoDB (for performance and data security) and the search tables being MyISAM (for performance on that particular workload and acknowledging the fact that, if that data was corrupted, it could be easily rebuilt) is an excellent fit.