By Michael Ross

This article was published in the print magazine Drupal Watchdog, Volume 3 Issue 1, 2013-04, on page 13, by Tag1 Publishing. The magazine was distributed at Drupalcon Portland, 2013-05-20. The article was also published on their website.

You might choose Drupal to create a simple "brochure" website, i.e., one with no e-commerce, workflows, configuration changes by administrators, or other functionality that calls for the recording in the database of all actions that occur within the system. The website may reside on an inexpensive shared hosting server, which can hinder the website's performance. In such a scenario, try turning off Drupal's built-in database logging (Administration > Reports > Recent log messages) by disabling the "Database logging" module (Administration > Modules). Thankfully, database (s)logging is sometimes avoidable!

Figure 1. Drupal Watchdog rabbit

Copyright © 2012 Michael J. Ross. All rights reserved.