From d3b023e835aeafe210ffa036eb84f862deb82dcd Mon Sep 17 00:00:00 2001 From: Graham Leggett Date: Sun, 16 Nov 2008 19:32:13 +0000 Subject: [PATCH] Clarify the documentation for mod_buffer to better explain where the buffer might be useful, and that buffering is not guaranteed to improve performance in all cases. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@718086 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_buffer.xml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/manual/mod/mod_buffer.xml b/docs/manual/mod/mod_buffer.xml index a4bc39ee0a..cd8aaf1559 100644 --- a/docs/manual/mod/mod_buffer.xml +++ b/docs/manual/mod/mod_buffer.xml @@ -58,6 +58,14 @@ AddOutputFilterByType INCLUDES;BUFFER text/html
+ The buffer filters read the request/response into + RAM and then repack the request/response into the fewest memory + buckets possible, at the cost of CPU time. When the request/response + is already efficiently packed, buffering the request/response could + cause the request/response to be slower than not using a buffer at + all. These filters should be used with care, and only where + necessary. + Filters -- 2.50.1