Problem/Motivation

The History service is sometimes slow. While working on #2081585: [META] Modernize the History module proposals were developed for using a memory cache in the history repository service.

Proposed resolution

Use a cache to minimise database access.

Remaining tasks

1. Decide on approach.
2. Implement

User interface changes

None.

API changes

None.

Data model changes

None.

Comments

jonathanshaw created an issue. See original summary.

jonathanshaw’s picture

jonathanshaw
Primary language English
Location Stroud, UK
commented

In #2081585-216: [META] Modernize the History module @Berdir wrote:

not fond of the cache tags. The entity cache tag is actually missing the entity type so that's kinda broken and both entity and user cache tags are only invalidated if a user or entity is deleted. That's pointless as nobody is going to request that information then. If we want to use a memory cache for this and not just a protected property (why, exactly?) then this actually seems like a good case to instantiate a separate bin and _not_ misuse the entity service, then you can just deleteAll() and be done with it.

jonathanshaw’s picture

jonathanshaw
Primary language English
Location Stroud, UK
commented
Issue summary: View changes

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Status: Active » Postponed

The History Module was approved for removal in #3336276: [Policy] Deprecate History module.

This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.

The deprecation work is in #3520462: [meta] Tasks to deprecate the History module and the removal work in #3520468: [meta] Tasks to remove History module.

History will be moved to a contributed project after the Drupal 12.x branch is open.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

longwave’s picture

longwave
he/him
Primary language English
Location UK
commented
Project: Drupal core » Node History
Version: main » 1.0.0
Component: history.module » Code
Status: Postponed » Active