Hi all,

Just throwing this out there. I have been using the Cache Router module to implement Memcache in Drupal 6.x. It says it "refactored" the Memcache API module to include Memcache support, which seems a bit odd. But it works.

But I notice the Memcache API project now has a stable point release ahead of Cache Router, and it will probably stay ahead of the curve, development wise, being able to focus on Memcache only as a caching mechanism...

I'm torn. If we decide to go with Memcache, should I ditch Cache Router in favour of the Memcache API, or stick with it so I can easily switch?

Your comments welcome! =)

--
http://www.drupaler.co.uk

Comments

catch’s picture

I like the idea behind cache_router, but I'd really prefer it as an API which modules like memcache could plug into rather than have them competing. I tried one of the early betas/alphas of cacherouter for D6 using APC as a bin - but hit a lot of fragmentation and segfault issues. Since set up memcache with memcache.module and it's been good so far - haven't yet compared it with the cacherouter version though and I don't really have a need for multiple caching mechanisms at least for the moment.

I'd be interested in whether people use the straight memcache.inc or memcache_db.inc which has the cache_* tables as a fallback. I switched to memcache_db.inc after discovering a missing space in my memcache init script was causing some of my bins not to start up properly, the fallback gives me some piece of mind, then I feel bad about the extra inserts, then I go back to liking having the fallback (this is for one of my personal projects, not a client site, so I've got a bit of room to play around with it).

damienmckenna’s picture

Drupal 5 site.. cacherouter gave me problems when trying to use it with the memcache bucket, and the supposed fix in v5.x-1.0b9 messed up my site quite thoroughly. Memcache, on the other hand, has just always worked.

--
Damien McKenna | Mediacurrent

greg.harvey’s picture