#30207: Optimise paginator for tables with massive records
-------------------------------------+-------------------------------------
Reporter: M. Javidan Darugar | Owner: M.
Type: | Javidan Darugar
Cleanup/optimization | Status: assigned
Component: Core (Other) | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Hello there,
Could you provide more details about which database backend is sped up
with this technique? I'm a bit surprised two queries perform faster than
one in this case because even if the first one would allows the usage of
an index only scan the tuples still have to be fetched in the end. The
query planner should be smart enough to chain the operations in a single
query. I suspect something else might be at play here such as the query to
''count'' the number of results.
By the way, the issue title should be changed to reflect what the
optimization technique is as right now it's pretty vague.
--
Ticket URL: <https://code.djangoproject.com/ticket/30207#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 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.fd9205b14bb5aa537f72397b1dab73d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
