#36439: Auth hashing blocks event loop if using asyncio
-------------------------------------+-------------------------------------
Reporter: Robert Aistleitner | Owner: (none)
Type: | Status: new
Cleanup/optimization |
Component: contrib.auth | Version: 5.2
Severity: Normal | Resolution:
Keywords: async, auth, | Triage Stage: Accepted
asyncio, performance |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Roelzkie):
Replying to [comment:4 Jake Howard]:
> A patch (PR), particularly with benchmarks, sounds great. The
`sync_to_async` call is probably doing most of the work - it's possible
there's no need for a dedicated threadpool just for this hashing. But
again, a patch and some benchmark figures will help make that decision.
Hello, I see the status of this ticket is **Accepted** without an owner. I
wonder if you can allow me to spend time doing a basic profiling for the
above-suggested solution, and make a comparison to help with your
decision. Thank you.
--
Ticket URL: <https://code.djangoproject.com/ticket/36439#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 visit
https://groups.google.com/d/msgid/django-updates/01070197b6780f95-65ca00ab-4542-4d56-a01e-e1290e2bed4f-000000%40eu-central-1.amazonses.com.
