#34746: High CPU/memory consumption when a 5XX is raised with large local
variables
--------------------------------------+------------------------------------
Reporter: Rémi Dupré | Owner: (none)
Type: Cleanup/optimization | Status: new
Component: Error reporting | Version: 4.2
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Natalia Bidart):
* type: Bug => Cleanup/optimization
* easy: 0 => 1
* stage: Unreviewed => Accepted
Comment:
I have managed to reproduce the issue, thank you for the example. Indeed
if `v = pprint(v)` is replaced by something that does not render the whole
variable, the memory and CPU usage do not spike.
Accepting so we can evaluate whether an alternative could be used instead
of `pprint` that would account for the size limit before printing.
--
Ticket URL: <https://code.djangoproject.com/ticket/34746#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/010701899d1dd6bd-ccafc963-4981-4fa5-8589-778af7b75051-000000%40eu-central-1.amazonses.com.
