#32174: Error page can sometimes be very slow
-------------------------------------+-------------------------------------
Reporter: boxed | Owner: (none)
Type: | Status: closed
Cleanup/optimization |
Component: Error reporting | Version: 3.1
Severity: Normal | Resolution: wontfix
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 boxed):
I disagree. Optimizing queries with prefetch or select related can be done
later. You are saying that we should always apply optimizations first just
in case a debug page is hit.
In any case, if you don't like the fix, would you be open to a change that
would break apart the big function my PR modifies so that this change can
be implemented locally without copy pasting that big function (risking
compatibility problems, missed bug fixes etc)?
--
Ticket URL: <https://code.djangoproject.com/ticket/32174#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/063.d0d0a3349fe53766812977d973c1b251%40djangoproject.com.
