id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
33157	Consider back-porting the fix of #32889 to version 3.2.x	Ryan Henning	nobody	"Prior to the fix for #32889 (and when deployed under an ASGI server, and for *synchronous* views), a single Django process would only serve one request at a time. Any blocking (e.g. for the ORM) during serving a single request would block _all other requests_ from being served. This caused us issues as we scaled up.

I've manually ported the fix for #32889 into our codebase and *WOOT* it works great!

We're running Django 3.2.7 and Python 3.7 (btw) and this back-port works well.

It seems that the fix is scheduled only for Django v4.x ... but I think this should be back-ported to v3.2.x so more people can benefit. It seems to work as-is, so the back-port *should* be easy."	New feature	new	HTTP handling	3.2	Normal				Unreviewed	0	0	0	0	0	0