#37129: Cache docs incompletely characterize when culling happens
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Type:
| Cleanup/optimization
Status: new | Component:
| Documentation
Version: 6.0 | Severity: Normal
Keywords: cache | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
See [https://forum.djangoproject.com/t/django-database-cache-untouched-
expired-entries-are-never-culled-unless-max-entries-is-reached/22679 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.)
--
Ticket URL: <https://code.djangoproject.com/ticket/37129>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019e7486b9bb-35ed99f8-3428-46ea-a1dd-46b999d212d9-000000%40eu-central-1.amazonses.com.
