Problem/Motivation

I'm updating a client site to 5.x from 2.x and rebuilding the entity usage table is taking a long time.

Proposed resolution

Entity revision caching added in #2620980: Add static and persistent caching to ContentEntityStorageBase::loadRevision() is causing issues.

Remaining tasks

There's no sensible way in core to disable revision caching a for a single process. Opened #3618977: Persistent revision caching needs a kill switch to discuss.

User interface changes

API changes

Data model changes

Issue fork entity_usage-3617820

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

alexpott created an issue. See original summary.

alexpott opened merge request !237

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
commented
Title: Investigate performance issues with updating from 2.x to 5.x » Disable entity revision caching when doing a bulk update
Issue summary: View changes
Status: Active » Needs review
csakiistvan’s picture

csakiistvan
Primary language Hungarian
Location Budapest, Hungary
commented
Assigned: Unassigned » csakiistvan
csakiistvan’s picture

csakiistvan
Primary language Hungarian
Location Budapest, Hungary
commented
Assigned: csakiistvan » Unassigned
Status: Needs review » Reviewed & tested by the community

✅ Tested and works — applied MR !237, ran ddev drush cr, truncated cache_entity and pressed "Recreate all entity usage statistics" on /admin/config/entity-usage/batch-update: cache_entity stays empty afterwards, while without the MR the same run left 13 revision entries behind. The bulk update no longer pollutes the persistent entity cache.

  • alexpott committed 2b22bddb on 5.x 
    task: #3617820 Disable entity revision caching when doing a bulk update...
alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
commented
Status: Reviewed & tested by the community » 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.