Currentlyasyncio tasks are stored in aWeakset, this is inefficient and in some cases causes bugs because of thread safety (#80788). In terms of memory usage it requires maintaining a full set and their corresponding weakref callback to cleanup objects when deallocated and finalized by the gc. In applications where tasks are created at fast pace this becomes a bottle neck, to mitigate this nowasyncio tasks will now be stored in a global double linked of tasks for cases where Task is a subclass of_asyncio.Task in other cases we still rely on the weakset. This reduces the work done by the gc speedups the execution and reduces memory usage. In some of my own benchmarks I have seen 15- 20% improvement and pyperformance benchmarks reflect roughly the same.

https://github.com/faster-cpython/benchmarking-public/blob/main/results/bm-20230805-3.13.0a0-1d32835/bm-20230805-linux-x86_64-kumaraditya303-linked_list-3.13.0a0-1d32835-vs-base.md

Updated:https://github.com/faster-cpython/benchmarking-public/tree/main/results/bm-20240622-3.14.0a0-4717aaa#vs-base

Linked PRs

• GH-107803: double linked list implementation for asyncio tasks #107804
• gh-107803: add whatsnew for asyncio double linked list implementation #120995
• gh-107803: fix thread safety issue in double linked list implementation #121007
• GH-107803: use circular double linked list #126577