From 0c326fdc031c7f4a4d5b7f32f6ea1b852489176f Mon Sep 17 00:00:00 2001 From: Adrian Chaves Date: Fri, 19 Jun 2026 16:57:48 +0200 Subject: [PATCH] Improve documentation wording --- docs/topics/practices.rst | 1 - docs/topics/settings.rst | 4 ++-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/topics/practices.rst b/docs/topics/practices.rst index 5253c1ed4..c54d0c85f 100644 --- a/docs/topics/practices.rst +++ b/docs/topics/practices.rst @@ -433,7 +433,6 @@ In this case, the spider spent about 45 seconds paused due to large responses in memory. You could: - Increase :setting:`RESPONSE_MAX_ACTIVE_SIZE` if your machine has enough RAM. -- Reduce :setting:`CONCURRENT_REQUESTS` to let responses be processed faster. - Check that your code doesn't hold strong references to :class:`~scrapy.http.Response` objects longer than necessary. diff --git a/docs/topics/settings.rst b/docs/topics/settings.rst index c00cb1d76..0fa2229a8 100644 --- a/docs/topics/settings.rst +++ b/docs/topics/settings.rst @@ -1723,8 +1723,8 @@ This counts both the size of response bodies that have passed through memory, and the :setting:`rough size ` of requests currently being downloaded. -When the total exceeds this value, Scrapy pauses scheduling new requests until -it drops below the limit. +When the total exceeds this value, Scrapy pauses sending new requests to the +downloader until it drops below the limit. If you set this to ``0``, the limit is disabled.