#37177: Performance issue in Async Middleware handling.
--------------------------------+---------------------------------------
Reporter: Carlton Gibson | Owner: Jacob Walls
Type: Bug | Status: assigned
Component: HTTP handling | Version: 6.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 Mykhailo Havelia):
Replying to [comment:7 Carlton Gibson]:
> @Jacob: great thanks! (I'm off on holiday so won't have time to process
it instantly)
>
> My half-thought was, if introspection is too clever:
>
> 1. Manually mark (affected) built in middleware as `async_capable =
False`
> 2. Deprecate `MiddlewareMixin.__acall__` implementation.
>
> And that might be sufficient?
>
That's a viable option, but it could break things for people who inherit
from the default middleware and rely on async_capable. We'd need to
double-check that.
https://github.com/django/new-features/issues/102 is another option for
solving this for CPU-bound middleware.
--
Ticket URL: <https://code.djangoproject.com/ticket/37177#comment:8>
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/0107019edb665fa8-42805d45-39a2-4f09-ac9f-6a59ad0456a8-000000%40eu-central-1.amazonses.com.
