Problem/Motivation

We offer an option to persist certain cache bins so their data will survive full cache clears. This is useful for data that is too expensive to recalculate every time the caches are cleared. However we also have an option to make the persistent caching strategy the default for all cache bins. This is not a good idea since the vast majority of cache bins in Drupal are for cheap data and retaining all of it will just fill up disk space.

Proposed resolution

Remove the option.

Issue fork filecache-3586839

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

pfrenssen created an issue. See original summary.

pfrenssen’s picture

Issue tags: +DevDaysAthens2026

  • pfrenssen committed 715b558c on 8.x-1.x
    feat: #3586839 Remove the option to use persistent caching as a default...
pfrenssen’s picture

Status: Active » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.