gh-112169: Documented getaddrinfo/getnameinfo default loop executor u…

…sage and implications. (#112191) Co-authored-by: Guido van Rossum <[email protected]> Co-authored-by: Kumar Aditya <[email protected]> Co-authored-by: Carol Willing <[email protected]>
python · Jun 24, 2024 · fc297b4 · fc297b4
1 parent 1500a23
commit fc297b4
Showing 1 changed file with 8 additions and 0 deletions.
diff --git a/Doc/library/asyncio-eventloop.rst b/Doc/library/asyncio-eventloop.rst
@@ -1155,6 +1155,14 @@ DNS
 
    Asynchronous version of :meth:`socket.getnameinfo`.
 
+.. note::
+   Both *getaddrinfo* and *getnameinfo* internally utilize their synchronous
+   versions through the loop's default thread pool executor.
+   When this executor is saturated, these methods may experience delays,
+   which higher-level networking libraries may report as increased timeouts.
+   To mitigate this, consider using a custom executor for other user tasks,
+   or setting a default executor with a larger number of workers.
+
 .. versionchanged:: 3.7
    Both *getaddrinfo* and *getnameinfo* methods were always documented
    to return a coroutine, but prior to Python 3.7 they were, in fact,