#32312: Performance decrease following implementation of ASGI handler and
coroutine-safety.
-------------------------------+--------------------------------------
Reporter: David Smith | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 3.0
Severity: Normal | Resolution:
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 Andrew Godwin):
I would not be surprised that the ASGI worked slowed down Django a little
bit - that was always going to be the compromise - and I perf-tested it
before and after the 3.1 view/request changes to see a negligible (~5%)
difference for sync runtimes.
However, I never _did_ performance test this older commit, and I agree
that the new Local class might well be to blame - it was built for safety
rather than speed (for obvious reasons), and there's likely some potential
there for optimisation. Particularly, it could likely do with some quick-
shortcuts out of its deeper codepaths if it knows there's nothing async
going on.
--
Ticket URL: <https://code.djangoproject.com/ticket/32312#comment:3>
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/066.8c11a7be85eae45d7adf062e99538a79%40djangoproject.com.
