You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when using object caches (in core or extensions) that write to a file the process of removing old cache keys is manual. This makes it easy for the object cache to bloat over time.
One idea to correct this is to allow the object cache to be flagged for auto-cleanup. Then, whenever a full build is completed (not partial builds) any unused keys in an object cache can be removed before the cache file is written.
The text was updated successfully, but these errors were encountered:
Currently when using object caches (in core or extensions) that write to a file the process of removing old cache keys is manual. This makes it easy for the object cache to bloat over time.
One idea to correct this is to allow the object cache to be flagged for auto-cleanup. Then, whenever a full build is completed (not partial builds) any unused keys in an object cache can be removed before the cache file is written.
The text was updated successfully, but these errors were encountered: