httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: apachen/htdocs/manual/misc perf-hp.html perf.html index.html
Date Thu, 06 Nov 1997 02:55:09 GMT
brian       97/11/05 18:55:09

  Modified:    htdocs/manual/misc perf.html index.html
  Added:       htdocs/manual/misc perf-hp.html
  Added notes about HP
  Revision  Changes    Path
  1.15      +1 -0      apachen/htdocs/manual/misc/perf.html
  Index: perf.html
  RCS file: /export/home/cvs/apachen/htdocs/manual/misc/perf.html,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- perf.html	1997/11/03 23:34:05	1.14
  +++ perf.html	1997/11/06 02:55:07	1.15
  @@ -26,6 +26,7 @@
   <LI><A HREF="#AUX">A/UX (Apple's UNIX)</A>
   <LI><A HREF="#BSD">BSD-based (BSDI, FreeBSD, etc)</A>
   <LI><A HREF="#DEC">Digital UNIX</A>
  +<LI><A HREF="perf-hp.html">HPUX</A>
   <LI><A HREF="#Linux">Linux</A>
   <LI><A HREF="#SGI">SGI</A>
   <LI><A HREF="#Solaris">Solaris</A>
  1.8       +6 -0      apachen/htdocs/manual/misc/index.html
  Index: index.html
  RCS file: /export/home/cvs/apachen/htdocs/manual/misc/index.html,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- index.html	1997/10/13 21:11:59	1.7
  +++ index.html	1997/11/06 02:55:07	1.8
  @@ -92,6 +92,12 @@
       performance on Digital UNIX systems.
  +        HREF="perf-hp.html"
  +       >Performance Notes (HPUX)</A>
  +   </DT>
  +   <DD>Email from an HP engineer on how to optimize HP-UX 10.20.
  +   </DD>
  +   <DT><A
          >Performance Notes (General)</A>
  1.1                  apachen/htdocs/manual/misc/perf-hp.html
  Index: perf-hp.html
  <title>Running a High-Performance Web Server on HPUX</title>
  <!-- Background white, links blue (unvisited), navy (visited), red (active) -->
  <A NAME="initial">
   <IMG SRC="../images/sub.gif" ALT="[APACHE DOCUMENTATION]">
    Apache HTTP Server Version 1.3
  <H1 ALIGN="CENTER">Running a High-Performance Web Server for HPUX</H1>
  Date: Wed, 05 Nov 1997 16:59:34 -0800
  From: Rick Jones &lt;<A HREF=""></A>&gt;
  Organization: Network Performance
  Subject: HP-UX tuning tips
  Here are some tuning tips for HP-UX to add to the tuning page.
  For HP-UX 9.X: Upgrade to 10.20<BR>
  For HP-UX 10.[00|01|10]: Upgrade to 10.20
  For HP-UX 10.20: 
  Install the latest cumulative ARPA Transport Patch. This will allow you
  to configure the size of the TCP connection lookup hash table. The
  default is 256 buckets and must be set to a power of two. This is
  accomplished with adb against the *disc* image of the kernel. The
  variable name is tcp_hash_size.
  How to pick the value? Examine the output of
  <A HREF=""></A> and see how many
  total TCP connections exist on the system. You probably want that number
  divided by the hash table size to be reasonably small, say less than 10.
  Folks can look at HP's SPECweb96 disclosures for some common settings.
  These can be found at <A HREF=""></A>. If an HP-UX system was
  performing at 1000 SPECweb96 connections per second, the TIME_WAIT time
  of 60 seconds would mean 60,000 TCP "connections" being tracked. 
  Folks can check their listen queue depths with
  <A HREF=""></A>.
  If folks are running Apache on a PA-8000 based system, they should
  consider "chatr'ing" the Apache executable to have a large page size.
  This would be "chatr +pi L <binary>." The GID of the running executable
  must have MLOCK priviledges. Setprivgrp(1m) should be consulted for
  assigning MLOCK. The change can be validated by running Glance and
  examining the memory regions of the server(s) to make sure that they
  show a non-trivial fraction of the text segment being locked.
  If folks are running Apache on MP systems, they might consider writing a
  small program that uses mpctl() to bind processes to processors. A
  simple pid % numcpu algorithm is probably sufficient. This might even go
  into the source code.
  If folks are concerned about the number of FIN_WAIT_2 connections, they
  can use nettune to shrink the value of tcp_keepstart. However, they
  should be careful there - certainly do not make it less than oh two to
  four minutes. If tcp_hash_size has been set well, it is probably OK to
  let the FIN_WAIT_2's take longer to timeout (perhaps even the default
  two hours) - they will not on average have a big impact on performance.
  There are other things that could go into the code base, but that might
  be left for another email. Feel free to drop me a message if you or
  others are interested.
  rick jones<BR>
  <A HREF=""></A>
   Apache HTTP Server Version 1.3
  <A HREF="./"><IMG SRC="../images/index.gif" ALT="Index"></A>
  <A HREF="../"><IMG SRC="../images/home.gif" ALT="Home"></A>

View raw message