In the current tree, the default was to use the pecl memcache and not the newer memcached. See #907614: Allow a choice of extension (and default to memcache due to bugs in memcached), and that references a bug in pecl memcached here. There is a duplicate of the above issue with other details here.

That duplicate issue has this comment: "The problem was that keys are not 0-terminated by libmemcached when using the binary protocol. Fixed that, and you may pull my fix from github (6abbe4b9f, devel branch)"

I could not find that on github, but it sounds like the bug might have been resolved in libmemcached. Can anyone confirm this? Just looking to revisit the advice to use memcache vs memcached. Thanks!

Comments

catch’s picture

catch
he/him
Primary language English
commented
Title: Default to memcached now? » Default to Memcache vs. Memcached extension?
Version: 6.x-1.9-rc1 » 7.x-1.x-dev

We've also seen performance regressions with memcached, so I think I'd keep this as is for now. Also the PECL memcache extension is being actively developed again so is not necessarily 'older' any more. Let's leave this open though in case others have thoughts.

jeffsheltren’s picture

jeffsheltren commented
Status: Active » Closed (works as designed)

Closing due to lack of activity. For the record, I've personally had some "strange" issues with using PECL memcached, so I generally prefer PECL memcache