Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Goal
- Built-in support for memcached as cache backend in Drupal core.
Battle plan
- kill prefixes: #1393392: Convert prefix cache clears to cache tags, then remove support for them
- update dmemcache.inc away from procedural
- port actual memcache.inc to D8
- #1202336: Add a key/value store API + also support Redis...
Related issues
Original summary
I think memcache is a must for all Drupal sites, especially large enterprise ones. I would be great if memcache was supported in drupal core without the need of a custom module. I would also like to see it go as far as being installed by default if the daemon is ready on installation.
It would also be great if it could be configured easily via the UI so that site builders on managed services with memcache could set it up in the best way for their site.
Comments
Comment #1
skottler CreditAttribution: skottler commentedI don't see the point in this - we already have a pluggable, OOP cache system that is really simple to extend. There are better, faster, and more replicable KV stores than memcache. Although it certainly is a standard right now, it probably won't be when 8 gets released.
Comment #2
droplet CreditAttribution: droplet commentedMYSQL 5.6 supports memcache, maybe something we can do with it.
Comment #3
sunComment #3.0
sunUpdated issue summary.
Comment #3.1
sunUpdated issue summary.
Comment #3.2
sunUpdated issue summary.
Comment #3.3
sunUpdated issue summary.
Comment #7
BerdirI'd propose we close this issue. We don't need to have everything in core and there's more than just memcache these days, redis has about 1k installations and memcache 1.5k.