#19276: ORM performance regression between 1.4.x and 1.5.x
-------------------------------------+-------------------------------------
Reporter: akaariai | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version:
Component: Database layer | 1.5-alpha-1
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by akaariai):
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
Comment:
One more regression spotted - query_select_related got hit by the above
regressions + another change made for fixing Oracle in select_related
cases. Commit: c159d9cec0baab7bbd04d5d51a92a51e354a722a, graph here:
http://users.tkk.fi/~akaariai/djbench/query_select_related/
A patch for the select_related case is available here:
https://github.com/akaariai/django/compare/fix_select_related_perf (the
reason for the regression was the repeated access to connections[using],
the fix dodges this and makes the code a little cleaner, too).
I am elevating this to release blocker. While the regressions aren't
really that severe, it is a good idea to check if we can easily fix the
performance regressions before the final release. If not, then lets just
close this ticket. So, release blocker as in "lets not forget to check
this before release".
--
Ticket URL: <https://code.djangoproject.com/ticket/19276#comment:1>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
