This site is archived.

Caching is a critical component of Drupal. But how does it work? This session will clearly explain the nuts and bolts of the caching system internals, present successful caching strategies, and show how caching solutions can change as Drupal scales up using memcache as an example.

One fortunate attendee will receive a free auto-throttle probability limiter.


John VanDyk

This session is intended for site architects and module developers. It will focus first on Drupal's built-in mechanisms for caching data and identify common pitfalls. Then it will broaden to show how swapping out the default caching layer for a memory-based cache such as memcache affects Drupal. We'll close with best practices for using memcache on single and multiple webservers and the case for including memory-based caching in Drupal 7.

Topics covered will include:

  • Getting, setting, and clearing cached data
  • When not to cache
  • Common Drupal configurations that defeat caching
  • Wielding the minimum cache lifetime
  • Introducing memcache
  • How memcache is different from standard caching
  • The right and wrong way to set up memcache
  • Monitoring memcache

After attending this session, you should come away with the knowledge to make informed decisions about caching strategy, and the ability to make a ton of cache. (Sorry.)

Related resources:

"Caching." Chapter 15, Pro Drupal Development, Second Edition.