#32785: Reduce culling frequency of database cache backend
--------------------------------------+------------------------------------
Reporter: Mike Lissner | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Cache system) | Version: dev
Severity: Normal | Resolution:
Keywords: cache, database | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Mike Lissner):
That works for me. In that case, I'll make this more concrete: Unless
further discussion here says otherwise, I intend to create a draft PR on
Github that adds a new property to the cache DB class. The property will
set CULL_EVERY_X (or maybe a better-named var) to 20, meaning that it'll
cull every time the cache gets to be 5% bigger than MAX_ENTRIES. (This
default is currently arbitrary, but seems fairly reasonable to me?)
I don't have any good sense of how to do the counter though. Any
suggestions that are better than a mod of a random number?
--
Ticket URL: <https://code.djangoproject.com/ticket/32785#comment:2>
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 on the web visit
https://groups.google.com/d/msgid/django-updates/066.bc08fd271903e2bc8e04155b522ad0ff%40djangoproject.com.
