#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
--------------------------------------+------------------------------------
Comment (by David Smith):
No need to apologise, the amount of patches yourself and Mariusz have got
in this week is incredible 🤯
I was looking at the new Local class and there is a comment about using
contextvars for storage, but this is dependent upon Python 3.7. I was
wondering if that could help as contextvars are written in C and so should
be faster? But I ran out of talent very quickly here 😃.
The other idea I had is, does Django know if there is any async going on?
If we know this can we decide to use threading.local or the asgi version?
(It seems logical to me but I'm well out of my depth here).
Finally, Yes, I'm happy to make progress with the benchmarking topic. It's
already starting to identify a few items and help prove some other
performance enhancements.
--
Ticket URL: <https://code.djangoproject.com/ticket/32312#comment:5>
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.b2095bfcfc586b4d66d287ad9e8382af%40djangoproject.com.
