public ChainedFastBackend::get($cid, $allow_invalid = FALSE) Returns data from the persistent cache. Parameters string $cid: The cache ID of the data to retrieve. bool $allow_invalid: (optional) If TRUE, a cache item may be returned even if it is expired or has been invalidated. Such items may sometimes be preferred, if the alternative is recalculating the value stored in the cache, especially if another concurrent request is already recalculating the same value. The "valid" property of the re

public ChainedFastBackend::garbageCollection() Performs garbage collection on a cache bin. The backend may choose to delete expired or invalidated items. Overrides CacheBackendInterface::garbageCollection File core/lib/Drupal/Core/Cache/ChainedFastBackend.php, line 261 Class ChainedFastBackend Defines a backend with a fast and a consistent backend chain. Namespace Drupal\Core\Cache Code public function garbageCollection() { $this->consistentBackend->garbageCollection(); $this

public ChainedFastBackend::deleteMultiple(array $cids) Deletes multiple items from the cache. If the cache items are being deleted because they are no longer "fresh", you may consider using invalidateMultiple() instead. This allows callers to retrieve the invalid items by calling get() with $allow_invalid set to TRUE. In some cases an invalid item may be acceptable rather than having to rebuild the cache. Parameters array $cids: An array of cache IDs to delete. Overrides CacheBackendInterface:

public ChainedFastBackend::deleteAll() Deletes all cache items in a bin. Overrides CacheBackendInterface::deleteAll See also \Drupal\Core\Cache\CacheBackendInterface::invalidateAll() \Drupal\Core\Cache\CacheBackendInterface::delete() \Drupal\Core\Cache\CacheBackendInterface::deleteMultiple() File core/lib/Drupal/Core/Cache/ChainedFastBackend.php, line 220 Class ChainedFastBackend Defines a backend with a fast and a consistent backend chain. Namespace Drupal\Core\Cache Code public func

public ChainedFastBackend::delete($cid) Deletes an item from the cache. If the cache item is being deleted because it is no longer "fresh", you may consider using invalidate() instead. This allows callers to retrieve the invalid item by calling get() with $allow_invalid set to TRUE. In some cases an invalid item may be acceptable rather than having to rebuild the cache. Parameters string $cid: The cache ID to delete. Overrides CacheBackendInterface::delete See also \Drupal\Core\Cache\CacheBac

The time at which the last write to this cache bin happened. Type: float File core/lib/Drupal/Core/Cache/ChainedFastBackend.php, line 79 Class ChainedFastBackend Defines a backend with a fast and a consistent backend chain. Namespace Drupal\Core\Cache Code protected $lastWriteTimestamp;

The fast cache backend. Type: \Drupal\Core\Cache\CacheBackendInterface File core/lib/Drupal/Core/Cache/ChainedFastBackend.php, line 72 Class ChainedFastBackend Defines a backend with a fast and a consistent backend chain. Namespace Drupal\Core\Cache Code protected $fastBackend;

The consistent cache backend. Type: \Drupal\Core\Cache\CacheBackendInterface File core/lib/Drupal/Core/Cache/ChainedFastBackend.php, line 65 Class ChainedFastBackend Defines a backend with a fast and a consistent backend chain. Namespace Drupal\Core\Cache Code protected $consistentBackend;

Type: string File core/lib/Drupal/Core/Cache/ChainedFastBackend.php, line 58 Class ChainedFastBackend Defines a backend with a fast and a consistent backend chain. Namespace Drupal\Core\Cache Code protected $bin;

Defines a backend with a fast and a consistent backend chain. In order to mitigate a network roundtrip for each cache get operation, this cache allows a fast backend to be put in front of a slow(er) backend. Typically the fast backend will be something like APCu, and be bound to a single web node, and will not require a network round trip to fetch a cache item. The fast backend will also typically be inconsistent (will only see changes from one web node). The slower backend will be something li