From 51b42be33e97a2ac4e6a100ee7b5936ac66c6040 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Igor=20Gali=C4=87?= Date: Tue, 31 Jul 2012 01:00:05 +0000 Subject: [PATCH] bump versions. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1367381 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/misc/perf-scaling.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/manual/misc/perf-scaling.xml b/docs/manual/misc/perf-scaling.xml index d84ebc6ee3a..dd131454141 100644 --- a/docs/manual/misc/perf-scaling.xml +++ b/docs/manual/misc/perf-scaling.xml @@ -59,7 +59,7 @@ What Will and Will Not Be Discussed

The session will focus on easily accessible configuration and tuning - options for Apache httpd 2.2 and 2.3 as well as monitoring tools. + options for Apache httpd 2.2 and 2.4 as well as monitoring tools. Monitoring tools will allow you to observe your web server to gather information about its performance, or lack thereof. We'll assume that you don't have an unlimited budget for @@ -883,9 +883,9 @@ same pre-forking process model that Apache 1.3 uses. The Worker MPM runs a smaller number of child processes, and spawns multiple request handling threads within each child process. In - 2.3+ MPMs are no longer hard-wired. They too can be exchanged + 2.4 MPMs are no longer hard-wired. They too can be exchanged via LoadModule. - The default MPM in 2.3 is the event MPM. + The default MPM in 2.4 is the event MPM.

The maximum number of workers, be they pre-forked child processes or threads within a process, is an indication of how -- 2.47.3