#29994: Document performance issues in FileBasedCache -----------------------------------------+------------------------ Reporter: matkoniecz | Owner: nobody Type: Uncategorized | Status: new Component: Documentation | Version: 2.1 Severity: Normal | Keywords: Triage Stage: Unreviewed | Has patch: 0 Needs documentation: 0 | Needs tests: 0 Patch needs improvement: 0 | Easy pickings: 0 UI/UX: 0 | -----------------------------------------+------------------------ https://docs.djangoproject.com/en/2.1/topics/cache/#filesystem-caching is not mentioning any problems with FileBasedCache
According to https://github.com/grantjenks/python-diskcache#diskcache- disk-backed-cache "Unfortunately the file-based cache in Django is essentially broken. The culling method is random and large caches repeatedly scan a cache directory which slows linearly with growth. Can you really allow it to take sixty milliseconds to store a key in a cache with a thousand items?" From my checking it seems to not be reported so far. According to https://github.com/grantjenks/python- diskcache/issues/93#issuecomment-442580191 "The deficiencies of FileBasedCache are too well known to require enumeration" but it would be nice to warn also developers unaware of this problems. -- Ticket URL: <https://code.djangoproject.com/ticket/29994> 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 django-updates+unsubscr...@googlegroups.com. To post to this group, send email to django-updates@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/053.fd5e91c509d69f7446f4e33a89a06350%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.