Closed (duplicate)
Project:
Memcache API and Integration
Version:
6.x-1.9
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
27 May 2011 at 07:48 UTC
Updated:
9 May 2012 at 23:46 UTC
I switched between PECL Memcache 3.0.4 and PECL Memcached 1.0.2 and time spent in Memcache increased hugely. I've attached a graph from New Relic that shows the increase under Memcached and the subsequent drop when I switched back to Memcache.
I used memcache locking and stampede protection (default settings) and enabled the binary protocol under Memcached. I'm running Ubuntu Lucid and Drupal 6.20 (no Pressflow).
Has anyone else experienced this performance difference?
| Comment | File | Size | Author |
|---|---|---|---|
| akeri.se - New Relic-1.jpg | 34.81 KB | henrrrik |
Comments
Comment #1
catchJust a note we now default to the Memcache extension in 6.x-1.9, and recommend against using the Memcached extensions since it has documented bugs that aren't fixed in any branches. I have seen the performance issue before, but iirc we didn't get much further than switching back to the Memcache extension in terms of tracking it down.
Comment #2
djbobbydrake commentedSeeing significant performance issues when upgrading from 6.x-1.5 to 6.x-1.9 (like 2-3 seconds difference in page load times in my local environment). We're using the Memcached extension, and would rather not have to modify our architecture to use the Memcache extension. Poor performance on 6.x-1.9 is preventing us from upgrading to 6.x-1.9. Hard for us to make an argument to our architecture team to switch up their architecture when the Memcached extension was working fine for 6.x-1.5.
Comment #3
djbobbydrake commentedFound that much of the performance hit was due to memcache not being able to set the theme registry cache. A separate ticket was opened here: http://drupal.org/node/1257768.
Comment #4
djbobbydrake commentedPosted a solution in that issue I mentioned: http://drupal.org/node/1257768. For the particular performance problem we were having, we had to enable compression (the 6.x-1.9 version disables it by default), in order to cash a large value in our theme registry.
Comment #5
jeffsheltren commentedI'm closing this since it's been addressed elsewhere.