Setting up memcache and memcached in Drupal

Memcache had always seemed like some magic black box to me until the last time I set it up and really took the time to understand what it does.

I'd say there are two main benefits to memcache:

  1. Reducing hits on the database - all of Drupal's normal caching can be set to store in memory instead of the database thereby reducing expensive inserts and large numbers of reads
  2. If you have your database on a different server then you will see a massive performance increase because cached data is stored on the web server and therefore you don't have the overhead of network IO

Setting up memcache consists of the following steps:

To install memcached and memcache:
sudo apt-get install php5-memcached php5-memcache

Then in your php.ini:

extension=memcache.so
memcache.hash_strategy="consistent"

Restart Apache and check your phpinfo() for memcache.

Then get the Drupal memcache module (you don't need to install it but you need the module in place). Once in place configure Drupal to use memcache by adding the following lines to your settings.php inside the $conf array (you may need to uncomment the open and close of the array:

'cache_inc' => './sites/all/modules/contrib/memcache/memcache.inc',
'memcache_servers' => array(
'127.0.0.1:11211' => 'default',
),
'memcache_bins' => array(
'cache' => 'default',
'cache_block' => 'default',
'cache_content' => 'default',
'cache_filter' => 'default',
'cache_form' => 'default',
'cache_menu' => 'default',
'cache_page' => 'default',
'cache_update' => 'default',
'cache_views' => 'default',
'session' => 'default',
'users' => 'default',
'cache_performance' => 'default',
),

Later on I might explain all the settings above, but essentially it tells Drupal what file to use to talk to memcache, where the server is and what tables to use memcache for.

How do you know it's working?

Memcache has several tools and you can telnet here and there but I've found the easiest way to know for sure is to check your cache tables aren't being populated. If you comment out the 'cache_inc' line in your settings.php then clear your cache or empty your cache table you should see it gets filled up as you browse your site. With the line uncommented and an empty table, you should find it stays empty. You will also see cache_set and cache_get queries drop out of the devel query logger.

Post new comment

By submitting this form, you accept the Mollom privacy policy.

User login

Author of...

  • @darthsteven or disabled javascript? 15 years 31 weeks ago
  • Having a look at Drupal 7 makes me wanna ditch my efforts to evaluate modx for 'smaller' sites. Is it familiarity or is Drupal just better? 15 years 36 weeks ago
  • @bridgecourt Modx 1.0 15 years 36 weeks ago
  • Giving Modx a go. First impressions: install 'ok', responsive javascript admin interface. with nice tree nav of site. Nod test = good. 15 years 36 weeks ago
  • Front End Drupal mentions the Textimage module. Will be giving that a try soon: http://2tu.us/m6n 15 years 39 weeks ago
  • Why haven't I found this before?!! Firebug for ie. My life just got a lot easier. http://2tu.us/li0 15 years 39 weeks ago
  • Drupal's looking good: http://bit.ly/rKrpS 15 years 39 weeks ago
  • Taking a look at kompozer. OS alternative to Dreamweaver for win, lin & mac :-) http://www.kompozer.net 15 years 41 weeks ago
Oliver Polden