Return-Path: X-Original-To: apmail-httpd-docs-archive@www.apache.org Delivered-To: apmail-httpd-docs-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 084A0222C for ; Wed, 27 Apr 2011 19:34:54 +0000 (UTC) Received: (qmail 48052 invoked by uid 500); 27 Apr 2011 19:34:53 -0000 Delivered-To: apmail-httpd-docs-archive@httpd.apache.org Received: (qmail 48013 invoked by uid 500); 27 Apr 2011 19:34:53 -0000 Mailing-List: contact docs-help@httpd.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: docs@httpd.apache.org List-Id: Delivered-To: mailing list docs@httpd.apache.org Received: (qmail 48005 invoked by uid 99); 27 Apr 2011 19:34:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Apr 2011 19:34:53 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.131] (HELO eos.apache.org) (140.211.11.131) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Apr 2011 19:34:50 +0000 Received: from eos.apache.org (localhost [127.0.0.1]) by eos.apache.org (Postfix) with ESMTP id A61CD5F5; Wed, 27 Apr 2011 19:34:29 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: Apache Wiki To: Apache Wiki Date: Wed, 27 Apr 2011 19:34:29 -0000 Message-ID: <20110427193429.50869.49044@eos.apache.org> Subject: =?utf-8?q?=5BHttpd_Wiki=5D_Update_of_=22PerformanceScalingUp=22_by_jmcg?= X-Virus-Checked: Checked by ClamAV on apache.org Dear Wiki user, You have subscribed to a wiki page or wiki category on "Httpd Wiki" for cha= nge notification. The "PerformanceScalingUp" page has been changed by jmcg. http://wiki.apache.org/httpd/PerformanceScalingUp?action=3Ddiff&rev1=3D7&re= v2=3D8 -------------------------------------------------- worth exploring it. There's also mod_dtrace available for httpd. = =3D=3D=3D mod_status =3D=3D=3D - The mod status module gives an overview of the server performance at a gi= ven + The mod_status module gives an overview of the server performance at a gi= ven moment. It generates an HTML page with, among others, the number of Apache processes running and how many bytes each has served, and the CPU load caused by httpd and the rest of the system. The Apache Software Foundation - uses mod status on its own [[http://apache.org/server-status|web site]]. + uses mod_status on its own [[http://apache.org/server-status|web site]]. If you put the `ExtendedStatus On` directive in your `httpd.conf`, the `mod_status` page will give you more informatio= n at the cost of a little extra work per request. @@ -534, +534 @@ have a virtual host serving SSL requests), it will activate the accept mu= tex to avoid internal conflicts. = - You can manipulate the accept mutex with the `AcceptMutex` directive. Be- + You can manipulate the accept mutex with the `AcceptMutex` directive. Bes= ides - sides turning the accept mutex off, you can select the locking mechanism.= Common + turning the accept mutex off, you can select the locking mechanism. Common locking mechanisms include fcntl, System V Semaphores and pthread locking. Not all are available on every platform, and their availability also depe= nds on compile-time settings. The various locking mechanisms may place specif= ic @@ -556, +556 @@ The usual mantra regarding RAM is "more is better". As discussed above, u= nused RAM is put to good use as file system cache. The Apache processes get bigger if you load more modules, especially if you use modules that gener= ate - dynamic page content within the processes, like PHP and mod perl. A large + dynamic page content within the processes, like PHP and mod_perl. A large configuration file-with many virtual hosts-also tends to inflate the proc= ess footprint. Having ample RAM allows you to run Apache with more child processes, which allows the server to process more concurrent requests. @@ -694, +694 @@ your catalog pages for red roses during the weeks leading up to Valentine= 's Day. When the user searches for red roses, they are served the pre-rendered pa= ge. Queries for, say, yellow roses will be generated directly from the databa= se. The - mod rewrite module included with Apache is a great tool to implement these + mod_rewrite module included with Apache is a great tool to implement these substitutions. = =3D=3D=3D Example: A Statically Rendered Blog =3D=3D=3D @@ -716, +716 @@ }}} This can be run periodically from Cron, after you upload content, etc. To make Apache substitute the statically rendered pages for the dynamic cont= ent, - we=E2=80=99ll use mod rewrite. This module is included with the Apache so= urce code, + we=E2=80=99ll use mod_rewrite. This module is included with the Apache so= urce code, but is not compiled by default. It can be built with the server by passin= g the option `--enable-rewrite[=3Dshared]` to the configure command. Many binary - distributions of Apache come with mod rewrite included. The following is = an + distributions of Apache come with mod_rewrite included. The following is = an example of an Apache virtual host that takes advantage of pre-rendered bl= og pages: {{{ @@ -758, +758 @@ rendered is served by the CGI. This means that individual entries, which = show the comments, are always served by the CGI which in turn means that your comment spam is always visible. This configuration also hides the Blosxom= CGI - from the user-visible URL in their Location bar. Mod rewrite is a fantast= ically + from the user-visible URL in their Location bar. mod_rewrite is a fantast= ically powerful and versatile module: investigate it to arrive at a configuratio= n that is best for your situation. = - =3D=3D Caching Content With mod cache =3D=3D + =3D=3D Caching Content With mod_cache =3D=3D - The mod cache module provides + The mod_cache module provides intelligent caching of HTTP responses: it is aware of the expiration timi= ng and - content requirements that are part of the HTTP specification. The mod cac= he + content requirements that are part of the HTTP specification. The mod_cac= he module caches URL response content. If content sent to the client is cons= idered cacheable, it is saved to disk. Subsequent requests for that URL will be = served directly from the cache. The provider module for mod_cache, mod_disk_cach= e, @@ -780, +780 @@ `Expires:`, mod_cache can not make the right decision on whether to cache= the content, serve it from cache or leave it alone. When testing content cach= ing, you may find that you need to modify your application or, if this is impo= ssible, - selectively disable caching for URLs that cause problems. The mod cache + selectively disable caching for URLs that cause problems. The mod_cache modules are not compiled by default, but can be enabled by passing the op= tion `--enable-cache[=3Dshared]` to the configure script. If you use a binary = distribution of Apache httpd, or it came with your port or package collection, it may = have --------------------------------------------------------------------- To unsubscribe, e-mail: docs-unsubscribe@httpd.apache.org For additional commands, e-mail: docs-help@httpd.apache.org