gh-112169: Documented getaddrinfo/getnameinfo default loop executor usage and implications. (#112191)

alex-kowalczyk · gvanrossum · kumaraditya303 · web-flow · commit fc297b4ba4c6 · 2024-06-24T08:35:02.000Z
Co-authored-by: Guido van Rossum &lt;gvanrossum@gmail.com&gt;
Co-authored-by: Kumar Aditya &lt;kumaraditya@python.org&gt;
Co-authored-by: Carol Willing &lt;carolcode@willingconsulting.com&gt;
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,
