#32772: Database cache counts the DB size twice at a performance penalty
--------------------------------------+------------------------------------
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
--------------------------------------+------------------------------------
Changes (by Simon Charette):
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
I'm not sure how widely used this backend is for large dataset but I agree
with you that both of these changes are no brainers.
I like the idea of having a cache option control the culling frequency and
I don't have a strong opinion on the implementation itself. Could we
possibly focus this ticket on the `COUNT` reduction off `cursor.rowcount`
and have another one track the culling frequency changes though?
FWIW this backend also suffers from other limitations that could be worth
fixing (#23326) if you're interested in doing that.
--
Ticket URL: <https://code.djangoproject.com/ticket/32772#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.f67022e87ff6b5c427d65512df321e30%40djangoproject.com.
