Consider to create a buffering / queued chained cache backend + buffering cache tags invalidator

Created on 14 September 2016, about 9 years ago

Updated 12 August 2025, about 1 month ago

The idea is to buffer all writes and invalidations, serve requests for the cache from static memory.

Have a flush() method to flush the memory backend contents to the database backend at the end, which disables the special functionality and it acts like a normal DB backend afterwards.

e.g.


class BufferingCacheBackend {

  function set($cid, $data, $tags) {
    static::$memory->set($cid, $data, $tags);
  }

  function invalidateTags($tags) {
    static::$actions['invalidateTags'][] = $tags;
  }

 // ... clear(), etc.

  function flushToDatabase() {
    foreach (static::$actions['invalidateTags'] as $tags) {
      $this->databaseCacheTagsInvalidator()->invalidateTags($tags);
   }
   foreach (static::$memory->getAll() as $cid => $data) {
     $this->database->set($item->cid, $item->data, $item->tags);
   }
  }
}

The above is just a "the PoC could look like this".

📌 Task

Status

Postponed: needs info

Version

11.0 🔥

Component

base system

Created by

🇩🇪Germany Fabianx

Live updates comments and jobs are added and updated live.

Performance
It affects performance. It is often combined with the Needs profiling tag.

stale-issue-cleanup
To track issues in the developing policy for closing stale issues, [Policy, no patch] closing older issues

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment about 1 month ago →
🇺🇸United States smustgrave
Thank you for creating this issue to improve Drupal.

We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024