From e30dc76250165a5959c9e70854cd26235693cb5f Mon Sep 17 00:00:00 2001 From: Brian Pane Date: Sat, 25 May 2002 06:58:39 +0000 Subject: [PATCH] Added EnableMMAP to performance tuning guide git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@95279 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/misc/perf-tuning.html | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/docs/manual/misc/perf-tuning.html b/docs/manual/misc/perf-tuning.html index 6e0aea4da3..a22a41b9cc 100644 --- a/docs/manual/misc/perf-tuning.html +++ b/docs/manual/misc/perf-tuning.html @@ -69,6 +69,8 @@ HostnameLookups
EnableMMAP
+ KeepAliveTimeout
MaxSpareServers
@@ -281,6 +283,35 @@ DirectoryIndex index.cgi index.pl index.shtml index.html determined by reading this single file, rather than having to scan the directory for files.

+

Memory-mapping

+ +

In situations where Apache 2.0 needs to look at the contents + of a file being delivered--for example, when doing server-side-include + processing--it normally memory-maps the file if the OS supports + some form of mmap(2). +

+ +

On some platforms, this memory-mapping improves performance. + However, there are cases where memory-mapping can hurt the performance + or even the stability of the httpd:

+ + + +

For installations where either of these factors applies, you + should use EnableMMAP off to disable the memory-mapping + of delivered files. (Note: This directive can be overridden on + a per-directory basis.)

+

Process Creation

Prior to Apache 1.3 the MinSpareServers, -- 2.40.0