From 0c220426317c1f81c8ec47c01e56c7319d1a48e1 Mon Sep 17 00:00:00 2001 From: Eric Covener Date: Sun, 13 Sep 2009 13:44:15 +0000 Subject: [PATCH] Provide a hint to those stuck with mod_mem_cache about coping with the per-process limitation. Add detail about another deficiency relative to disk_cache [1 variant at a time]. PR 47783 Reported By: Stoehr Sukachevin git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@814313 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_mem_cache.html.en | 6 +++++- docs/manual/mod/mod_mem_cache.xml | 7 ++++++- 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a/docs/manual/mod/mod_mem_cache.html.en b/docs/manual/mod/mod_mem_cache.html.en index ab356a674c4..ec6b736dcce 100644 --- a/docs/manual/mod/mod_mem_cache.html.en +++ b/docs/manual/mod/mod_mem_cache.html.en @@ -42,7 +42,11 @@

Note

In most cases mod_disk_cache should be the preferred choice. This is explained further in the Caching Guide. In particular, - this module's cache is per-process.
+ this module's cache is per-process, which can be partially + mitigated by configuring threaded MPMS to use fewer child processes + via configuration of larger values for ThreadsPerChild. This module's cache is + also limited to storing a single variant (see HTTP Vary: header) of each + resource in the cache.

Directives