#33158: Severely degraded performance under ASGI compared to the typical WSGI
deployment pattern
-------------------------------------+-------------------------------------
Reporter: Ryan Henning | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: HTTP handling | Version: 3.2
Severity: Normal | Resolution: duplicate
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: => duplicate
Comment:
Hi Ryan — sorry, this is just the same request as #33157.
The use of `ThreadSensitiveContex` from #32889 doesn't qualify for a
backport. The bottom line is we don't backport arbitrary new features into
released versions of Django. That does mean that folks need to upgrade to
get the benefits of new features (which is the negative) but it's also a
large part of why Django is so stable and reliable (the pro). On balance
it's not worth the regression risk, and so the backport policy is as it
is. I hope that makes sense.
In any case the fix from #32889 is not compatible with the Python support
matrix of 3.2.
--
Ticket URL: <https://code.djangoproject.com/ticket/33158#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.0f3cceac6cd7d0af65743c2cd4e39010%40djangoproject.com.
