Problem/Motivation

The prefix cache was introduced with a cache collector, but there's no need for that as we generally only expect one lookup per request, not multiple, which is what a a cache collector is useful for.

Doing specific queries means less data needs to be loaded and we can remove the limit setting entirely, it is unlikely to grow to a point where that becomes an issue.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork redirect-3578648

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:

About issue forks

Comments

berdir created an issue. See original summary.

berdir opened merge request !187

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Active » Needs review

  • berdir committed 93a8757a on 8.x-1.x 
    feat: #3578648 Change prefix list cache to their own distinct cache...
berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Needs review » Fixed

Now that this does possibly quite a few different cache entries and I've removed with size limit since that no longer makes sense, I decided to switch to the cache_data bin. Means we do a persistent cache lookup on every request, but it's still avoids the dynamic redirect lookup on many cases.

Merged.

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.