Goal

  • Built-in support for memcached as cache backend in Drupal core.

Battle plan

  1. kill prefixes: #1393392: Convert prefix cache clears to cache tags, then remove support for them
  2. update dmemcache.inc away from procedural
  3. port actual memcache.inc to D8
  4. #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

skottler’s picture

I 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.

droplet’s picture

MYSQL 5.6 supports memcache, maybe something we can do with it.

sun’s picture

Title: Memcache support in core » [meta] Memcached support in core
Issue tags: +Killer Developer Features, +API addition
sun’s picture

Issue summary: View changes

Updated issue summary.

sun’s picture

Issue summary: View changes

Updated issue summary.

sun’s picture

Issue summary: View changes

Updated issue summary.

sun’s picture

Issue summary: View changes

Updated issue summary.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Berdir’s picture

Issue summary: View changes
Status: Active » Closed (won't fix)

I'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.