From b3ff374aed521f7e26786fd28b4a9cedda7f3efa Mon Sep 17 00:00:00 2001
From: majiayu000 <1835304752@qq.com>
Date: Thu, 11 Dec 2025 14:07:01 +0800
Subject: [PATCH] Update memory docs for threading max_queue parameter

The threading implementation now has a max_queue parameter with the
same semantics as the asyncio implementation. Update the documentation
to reflect this change.

Fixes #1664
---
 docs/topics/memory.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/topics/memory.rst b/docs/topics/memory.rst
index 61b1113e2..acf1b6dac 100644
--- a/docs/topics/memory.rst
+++ b/docs/topics/memory.rst
@@ -152,6 +152,6 @@ and :func:`~asyncio.server.serve` varies across implementations.
   use up to 4 bytes of memory per character, the queue may use up to ``4 *
   max_size * max_queue`` bytes of memory. By default, this is 128 MiB.
 
-* In the :mod:`threading` implementation, there is no queue of incoming
-  messages. The ``max_queue`` argument doesn't exist. The connection keeps at
-  most one message in memory at a time.
+* In the :mod:`threading` implementation, ``max_queue`` is the high-water mark
+  of a queue of incoming frames. It defaults to 16 frames. It has the same
+  semantics as in the new :mod:`asyncio` implementation described above.