bpo-34134: Advise to use imap or imap_unordered when handling long iterables. (gh...

(cherry picked from commit 3bab40db96efda2e127ef84e6501fda0cdc4f5b8)

Co-authored-by: Windson yang <wiwindson@outlook.com>

diff --git a/Doc/library/multiprocessing.rst b/Doc/library/multiprocessing.rst
index c50625dda32019bc93d6bcea0568bce1f5216031..6ed8f211f361d843ee5556d016805da34acc568a 100644 (file)
--- a/Doc/library/multiprocessing.rst
+++ b/Doc/library/multiprocessing.rst
@@ -2148,6 +2148,10 @@ with the :class:`Pool` class.
       the process pool as separate tasks.  The (approximate) size of these
       chunks can be specified by setting *chunksize* to a positive integer.
 
+      Note that it may cause high memory usage for very long iterables. Consider
+      using :meth:`imap` or :meth:`imap_unordered` with explicit *chunksize*
+      option for better efficiency.
+
    .. method:: map_async(func, iterable[, chunksize[, callback[, error_callback]]])
 
       A variant of the :meth:`.map` method which returns a result object.
@@ -2166,7 +2170,7 @@ with the :class:`Pool` class.
 
    .. method:: imap(func, iterable[, chunksize])
 
-      A lazier version of :meth:`map`.
+      A lazier version of :meth:`.map`.
 
       The *chunksize* argument is the same as the one used by the :meth:`.map`
       method.  For very long iterables using a large value for *chunksize* can