#20577: Make prefetch_related faster by lazily creating related querysets
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Database layer | Resolution:
(models, ORM) | Triage Stage: Accepted
Severity: Normal | Needs documentation: 0
Keywords: | Patch needs improvement: 1
Has patch: 1 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
The approach in #17001 (prefetch custom querysets) will provide the
speedup promised in this ticket. Unfortunately the speedup is only
available to custom prefetches, not ordinary
.prefetch_related('some_related_set').
I am going to do a wait-and-see on this ticket, changes required for fast
prefetches directly into querysets require some hacks. The hacks needed:
create QuerySet.query lazily, and have a "on_query_creation_ops" QuerySet
attribute, that is things that are ran when the inner query is created.
I am going to leave this in accepted status - if a suitably clean patch is
written I think speeding up prefetch_related is a good idea.
--
Ticket URL: <https://code.djangoproject.com/ticket/20577#comment:5>
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/066.2576a8b4a96b054d3beb0817d2aa4465%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
