#32312: Performance decrease following implementation of ASGI handler and
coroutine-safety.
--------------------------------------+------------------------------------
Reporter: David Smith | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: 3.0
Severity: Normal | Resolution:
Keywords: async | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Carlton Gibson):
* keywords: => async
* type: Uncategorized => Cleanup/optimization
* component: Uncategorized => Core (Other)
* stage: Unreviewed => Accepted
Comment:
Hey David, sorry for the delay triaging this (3.2... 🙂) — It's a bit
unspecific as to what we'll do but let's accept this as a tracking ticket
for now, and we can either do sub-tickets or hang things on here.
You already did 622fcb81199864cad1ec9d0b25820a96ef3f586f which is super.
Can I just say, great work you're doing profiling and setting up the `asv`
runs, and the running django bench, and ... 🙂
Please do carry that on as you can, it's phenomenally helpful for you to
break the ground there!
🏅
--
Ticket URL: <https://code.djangoproject.com/ticket/32312#comment:4>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.0833c635557ba1f5059fd2190228aa98%40djangoproject.com.
