#30984: Cache culling.
-------------------------------------+-------------------------------------
Reporter: Martin Ennemoser | Owner: nobody
Type: Uncategorized | Status: closed
Component: Core (Cache system) | Version: 2.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by felixxm):
* status: new => closed
* component: Uncategorized => Core (Cache system)
* resolution: => invalid
Comment:
> I noticed that there is a cull() method that randomly deletes my cache
files. This is horrible since my users don't get the cached results
anymore and have to wait very long until they get the calculated result.
> Don't you consider this cull() method dangerous?
Cache is to cache values, and all cache system have limited capacity, so
to create a space for new values we need to remove old entries, that's why
culling is necessary. Cache backends implement their own culling strategy
(see [https://docs.djangoproject.com/en/2.2/topics/cache/#cache-arguments
documentation]). You can increase `MAX_ENTRIES`, but I think that you're
using cache in a wrong way. Nevertheless I don't see here any issue in
Django.
Closing per TicketClosingReasons/UseSupportChannels
--
Ticket URL: <https://code.djangoproject.com/ticket/30984#comment:1>
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/063.9809c9ce3e30acf8d4c141ea8e9fe0ee%40djangoproject.com.
