Use LRU Cache for static entity cache

Created on 8 January 2025, 14 days ago

Problem/Motivation

See #1199866: Add an in-memory LRU cache β†’ - let's use that code here. Postponing on that one...

Proposed resolution

Remaining tasks

User interface changes

Introduced terminology

API changes

Data model changes

Release notes snippet

πŸ“Œ Task
Status

Postponed

Version

11.0 πŸ”₯

Component

entity system

Created by

πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @alexpott
  • Merge request !10845Resolve #3498154 "On top of 1199866" β†’ (Open) created by alexpott
  • πŸ‡¬πŸ‡§United Kingdom catch

    Either in this issue or a follow-up, we should remove or modify MigrateExecutable::attemptMemoryReclaim()

  • πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

    alexpott β†’ changed the visibility of the branch 3498154-use-lru-cache to hidden.

  • heddn Nicaragua

    re: slot count:

    From #1199866-84: Add an in-memory LRU cache β†’ , the thought was that this should be a much higher number then 300. So it is nice to see a number of 1000. Do we know if smaller hosting, e.g. an entry level pantheon plan will hold 1000 entity slots for 5-6 fields on a node or paragraph?

  • πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

    @heddn well atm the moment the number of slots in your cache is infinite so this is not really making anything worse. 5-6 fields on node is not that much - I tried to get the amount of memory used by a node on a production site with a complex data model. I think it might in the realms of 0.2mb per node... so a 1000 of them is about 200mb which is well within what I would expect you to be running a migrate job with. I expect that most sites nodes would take up considerably less space.

Production build 0.71.5 2024