#36863: Under WSGI, multiple calls to asgiref.sync.async_to_sync within the same
request do not share the same event loop.
-------------------------------------+-------------------------------------
Reporter: Mykhailo Havelia | Owner: Vishy
Type: | Algo
Cleanup/optimization | Status: closed
Component: HTTP handling | Version: 6.0
Severity: Normal | Resolution: needsinfo
Keywords: async, wsgi | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* resolution: => needsinfo
* status: assigned => closed
* type: Bug => Cleanup/optimization
Comment:
Thanks Mykhalio. Can you help me quantify the performance impact? I'd like
to know the upside for async users as well as the downside for WGSI users
who have no async middleware or signals.
I notice your draft PR for the `WSGIHandler` has a nested function. We're
starting to see tickets along the lines of "X created nested functions
that take a gc pass to free". My understanding is that this is much less
of a worry on Python 3.14 now that we have incremental gc, but still. I
just want to know what WSGI-only users are paying.
Happy for you to reopen for another look with those details in hand, but
full disclosure we're going to need a few more +1s from knowledgable
parties to accept.
--
Ticket URL: <https://code.djangoproject.com/ticket/36863#comment:9>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019c0beffc9c-6debc9ec-e36a-4192-a664-70fdf3446ef1-000000%40eu-central-1.amazonses.com.
