#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
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: new => closed
* resolution: => wontfix
Comment:
Hi Anders. Thanks for the report.
Slowness here is a symptom of chained ORM lookups, rather than the
exception reporter per se. It's not something that we'd want to mask in
general, because you **want** to notice it, so you can optimize your
application.
If you do want to apply it yourself, your suggestion is the perfect case
for the [https://docs.djangoproject.com/en/3.1/ref/settings/#default-
exception-reporter DEFAULT_EXCEPTION_REPORTER] setting introduced in
Django 3.1. Apply your cached pretty printer in a subclass and use it in
your project.
I hope that makes sense.
--
Ticket URL: <https://code.djangoproject.com/ticket/32174#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 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.363e64f7062a9ae15f308c71d7257b69%40djangoproject.com.
