Optimizing InnoDB for Watchdog table in D5?

Events happening in the community are now at Drupal community events on www.drupal.org.
damienmckenna's picture

So supposing you have several sites on D5 that won't get upgraded to D6 (to take advantage of the syslog support) for several months yet due to workload, what are good ways to optimize InnoDB so that Watchdog can write faster, i.e more concurrent INSERT statements, rather than taking down the site if things get fubar'd? Thanks :)

Comments

Why InnoDB?

kbahey's picture

First, he patch for watchdog/syslog has been backported to Drupal 5 in this issue http://drupal.org/node/149341

Second, why InnoDB for watchdog? You don't need such a high overhead engine for it, do you? We never do an UPDATE on watchdog.

Can't you use something like Archive here? See this http://dev.mysql.com/tech-resources/articles/storage-engine.html

Note: Archive does not support DELETE though. So you have to change the pruning code if that causes errors. But chances are, MySQL will just ignore that DELETE does nothing.

Drupal performance tuning, development, customization and consulting: 2bits.com, Inc..
Personal blog: Baheyeldin.com.

Drupal performance tuning, development, customization and consulting: 2bits.com, Inc..
Personal blog: Baheyeldin.com.

Thanks!

damienmckenna's picture

kbahey: thanks for that, especially the backported code, I hadn't found that in my searches and we'll definitely go for it.

High performance

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: