Created on 28 September 2010, over 14 years ago
Updated 9 April 2025, 13 days ago

Goal

Only generate diffs once during a reasonable period of time, and do it in advance, when there is low load, if possible.

Depends on

Plan

  • If an entity revision is created, updated or deleted; then queue the generation of diffs.
  • Purge cache entries that haven't been accessed within storage size, limit time.

Aside

ConfigEntities are not revisioned, so separate is #1821548: Add a "diff" of some kind to the CMI UI .

Original Body - Modified

I recently started using the diff module and find that it's extremely slow on some pages. For example, on my computer a "node/383/revisions/view/385/998" page is taking more than 40 seconds CPU time to generate. I used XDebug and kcachegrind and found that 90% of the time is spent in the diff algorithm.

Feature request
Status

Postponed: needs info

Version

11.0 🔥

Component

entity system

Created by

🇨🇦Canada yang_yi_cn

Live updates comments and jobs are added and updated live.
  • stale-issue-cleanup

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

Sign in to follow issues

Comments & Activities

Not all content is available!

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

  • 🇺🇸United States smustgrave

    Thank you for sharing your idea for improving Drupal.

    We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. 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!

Production build 0.71.5 2024