httpd-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Httpd Wiki] Update of "PerformanceScalingUp" by jmcg
Date Wed, 27 Apr 2011 19:34:29 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Httpd Wiki" for change notification.

The "PerformanceScalingUp" page has been changed by jmcg.
http://wiki.apache.org/httpd/PerformanceScalingUp?action=diff&rev1=7&rev2=8

--------------------------------------------------

  worth exploring it. There's also mod_dtrace available for httpd.
  
  === mod_status ===
- The mod status module gives an overview of the server performance at a given
+ The mod_status module gives an overview of the server performance at a given
  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 information at
  the cost of a little extra work per request.
@@ -534, +534 @@

  have a virtual host serving SSL requests), it will activate the accept mutex 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. Besides
- 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 depends
  on compile-time settings. The various locking mechanisms may place specific
@@ -556, +556 @@

  The usual mantra regarding RAM is "more is better". As discussed above, unused
  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 generate
- 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 process 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 page.
  Queries for, say, yellow roses will be generated directly from the database. 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.
  
  === Example: A Statically Rendered Blog ===
@@ -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 content,
- we’ll use mod rewrite. This module is included with the Apache source code,
+ we’ll use mod_rewrite. This module is included with the Apache source code,
  but is not compiled by default. It can be built with the server by passing the
  option `--enable-rewrite[=shared]` 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 blog
  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 fantastically
+ from the user-visible URL in their Location bar. mod_rewrite is a fantastically
  powerful and versatile module: investigate it to arrive at a configuration that is
  best for your situation.
  
- == Caching Content With mod cache ==
+ == Caching Content With mod_cache ==
- The mod cache module provides
+ The mod_cache module provides
  intelligent caching of HTTP responses: it is aware of the expiration timing and
- content requirements that are part of the HTTP specification. The mod cache
+ content requirements that are part of the HTTP specification. The mod_cache
  module caches URL response content. If content sent to the client is considered
  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_cache,
@@ -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 caching,
  you may find that you need to modify your application or, if this is impossible,
- 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 option
  `--enable-cache[=shared]` 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


Mime
View raw message