#37129 new Cleanup/optimization

Cache docs incompletely characterize when culling happens

Reported by: Jacob Walls Owned by:
Component: Documentation Version: 6.0
Severity: Normal Keywords: cache
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

See forum post: the cache docs incompletely describe how expired entries are culled:

Instead, expired cache entries are culled each time add(), set(), or touch() is called.

"Each time" neglects the role of MAX_ENTRIES here. (You have to exceed MAX_ENTRIES before any culling is done.)

Change History (0)

Note: See TracTickets for help on using tickets.
Back to Top