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
37165	Update Async Topic Docs	Carlton Gibson	Carlton Gibson	"The [https://docs.djangoproject.com/en/6.0/topics/async/ Asynchronous support] topic doc was written when we first introduced async support. It's outdated, and the warnings it gives are misleadingly negative. Time to refresh it. 

The main problems are: 

1. It strongly implies that Django's asynchronous story is unfinished. It's **often** liked to in blog posts. And it's totally misleading. The user API is essentially finished. From the PR: """"""Many parts of Django provide asynchronous APIs, including :ref:`the ORM <async-queries>`, the cache framework, authentication, sessions, mail, and signals. For other code, the :func:`sync_to_async` adapter is a low-cost bridge (see :ref:`async_performance`).""""""

2. The performance warnings are severely outdated. `sync_to_async`/`async_to_sync` usage is in the order or microseconds with modern versions of Python. This plays directly into implementation considerations where we're constantly pulled towards duplicating whole code trees, on the mistaken assumption that `sync_to_async` usage (in particular) incurs a (relatively) massive performance hit. 

3. It makes no mention of the remaining async difficulties — such as concurrent DB queries — which are **not Django specific**. In particular connection pooling is the appropriate lever to increase throughput, regardless of whether you're using Django, any other async orm, or raw connections by hand. (The current phrasing implies it's the ORM that's at fault here: it's not!) 

The topic doc here is a big source of the negative narrative about Django's async story. It's time to correct that. 

"	Cleanup/optimization	assigned	Documentation	6.0	Normal				Unreviewed	1	0	0	0	0	0