#8408: Add a new meta option: don't do count(*) in admin
-------------------------------+------------------------------------
Reporter: lidaobing | Owner: oinopion
Type: New feature | Status: assigned
Component: contrib.admin | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 1 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by Cerin):
+1 for this feature. I have a few databases with tables containing tens of
millions of records, and browsing them in Django is painfully slow, even
with caching and extensive indexing. These sections of admin takes
*minutes* to load, and DDT is telling me that around 90% of the load time
is just from a single "SELECT COUNT(*) ..." to display the total result
count, which I don't care about.
Yes, both PostgreSQL and MySQL have tricks for approximate counts, but
only for total tables sizes, which doesn't help once you begin filtering.
And can confirm that using InfinitePaginator from django-pagination and
specifying a custom paginator=InfinitePaginator in your modeladmin does
not work because admin still expects to receive a valid count, which
causes InfinitePaginator to throw NotImplementedError exceptions.
--
Ticket URL: <https://code.djangoproject.com/ticket/8408#comment:38>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.6e7dbd385e0ca5e5f4113e7d07be6d7c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.