You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ma...@apache.org on 2001/07/23 14:24:31 UTC
cvs commit: httpd-docs-1.3/htdocs/manual/misc perf-hp.html
martin 01/07/23 05:24:31
Modified: htdocs/manual/misc perf-hp.html
Log:
Collapse the expanded footer.html again
Revision Changes Path
1.6 +38 -47 httpd-docs-1.3/htdocs/manual/misc/perf-hp.html
Index: perf-hp.html
===================================================================
RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/misc/perf-hp.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- perf-hp.html 1998/10/23 07:43:09 1.5
+++ perf-hp.html 2001/07/23 12:24:31 1.6
@@ -1,42 +1,42 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
-<TITLE>Running a High-Performance Web Server on HPUX</TITLE>
-</HEAD>
+<html>
+<head>
+<title>Running a High-Performance Web Server on HPUX</title>
+</head>
<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
-<BODY
- BGCOLOR="#FFFFFF"
- TEXT="#000000"
- LINK="#0000FF"
- VLINK="#000080"
- ALINK="#FF0000"
+<body
+ bgcolor="#ffffff"
+ text="#000000"
+ link="#0000ff"
+ vlink="#000080"
+ alink="#ff0000"
>
-<A NAME="initial"> </A>
+<a name="initial"> </A>
<!--#include virtual="header.html" -->
-<H1 ALIGN="CENTER">Running a High-Performance Web Server for HPUX</H1>
+<h1 align="center">Running a High-Performance Web Server for HPUX</h1>
-<PRE>
+<pre>
Date: Wed, 05 Nov 1997 16:59:34 -0800
-From: Rick Jones <<A HREF="mailto:raj@cup.hp.com">raj@cup.hp.com</A>>
+From: Rick Jones <<a href="mailto:raj@cup.hp.com">raj@cup.hp.com</a>>
Reply-To: raj@cup.hp.com
Organization: Network Performance
Subject: HP-UX tuning tips
-</PRE>
+</pre>
Here are some tuning tips for HP-UX to add to the tuning page.
-<P>
+<p>
-For HP-UX 9.X: Upgrade to 10.20<BR>
+For HP-UX 9.X: Upgrade to 10.20<br>
For HP-UX 10.[00|01|10]: Upgrade to 10.20
-<P>
+<p>
For HP-UX 10.20:
-<P>
+<p>
Install the latest cumulative ARPA Transport Patch. This will allow you
to configure the size of the TCP connection lookup hash table. The
@@ -48,26 +48,26 @@
quantity, not "w" to write a 16 bit value when patching the disc image because
the tcp_hash_size variable is a 32 bit quantity.
-<P>
+<p>
How to pick the value? Examine the output of
-<A HREF="ftp://ftp.cup.hp.com/dist/networking/tools/connhist">
-ftp://ftp.cup.hp.com/dist/networking/tools/connhist</A> and see how many
+<a href="ftp://ftp.cup.hp.com/dist/networking/tools/connhist">
+ftp://ftp.cup.hp.com/dist/networking/tools/connhist</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="http://www.specbench.org/">
-http://www.specbench.org/</A>. If an HP-UX system was
+These can be found at <a href="http://www.specbench.org/">
+http://www.specbench.org/</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.
-<P>
+<p>
Folks can check their listen queue depths with
-<A HREF="ftp://ftp.cup.hp.com/dist/networking/misc/listenq">
-ftp://ftp.cup.hp.com/dist/networking/misc/listenq</A>.
+<a href="ftp://ftp.cup.hp.com/dist/networking/misc/listenq">
+ftp://ftp.cup.hp.com/dist/networking/misc/listenq</a>.
-<P>
+<p>
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.
@@ -77,14 +77,14 @@
examining the memory regions of the server(s) to make sure that they
show a non-trivial fraction of the text segment being locked.
-<P>
+<p>
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.
-<P>
+<p>
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
@@ -93,30 +93,21 @@
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.
-<P>
+<p>
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.
-<P>
+<p>
sincerely,
-<P>
+<p>
-rick jones<BR>
-<A HREF="http://www.cup.hp.com/netperf/NetperfPage.html">
-http://www.cup.hp.com/netperf/NetperfPage.html</A>
+rick jones<br>
+<a href="http://www.cup.hp.com/netperf/NetperfPage.html">
+http://www.cup.hp.com/netperf/NetperfPage.html</a>
-<HR>
-
-<H3 ALIGN="CENTER">
- Apache HTTP Server Version 1.3
-</H3>
-
-<A HREF="./"><IMG SRC="../images/index.gif" ALT="Index"></A>
-<A HREF="../"><IMG SRC="../images/home.gif" ALT="Home"></A>
-
-</BODY></HTML>
-
+<!--#include virtual="footer.html" -->
+</body></html>