Mailing-List: contact test-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: test-dev@httpd.apache.org
Sender: gregames@smtp2.southeast.rr.com
Message-ID: <3D5D4C1D.80BB421B@apache.org>
Date: Fri, 16 Aug 2002 15:01:49 -0400
From: Greg Ames <gregames@apache.org>
MIME-Version: 1.0
To: Ian Holsman <ianh@apache.org>
CC: test-dev@httpd.apache.org
Subject: Re: mod_specweb99 debugging...
References: <3D5C6F24.ECE6E59F@west.sun.com> <3D5D05A0.C58C74BF@apache.org>
 <3D5D256E.5090500@apache.org> <3D5D2CBF.CAB4C134@apache.org>
 <3D5D3450.7090704@apache.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Ian Holsman wrote:

> i'm just about to talk to ***** who are going to do some static specweb
> tests with apache2
> any tips you would like to share with them ???

yeah.  

* When you source the shrc file, don't expect to see any output.  It just sets
some envvars.

* Look at the SPECWeb99 results page to see how some of the winning entries have
tuned the servers.  Also notice how many client boxes and how many/what kind of
NICs they are using. 

* The harder you drive the server, the more disk space you will need.  SPECWeb99
touches more files as you ramp up the number of concurrent connections.  There
is a formula here: http://www.spec.org/osg/web99/docs/users_guide.html#Pre-Inst 
Plus you need disk space for logs proportional to the load.

* I wouldn't be surprised if there are bugs or bottlenecks in mod_specweb99
itself, since it was only recently open sourced.  Please feed back any
info/patches to this list.  But you don't need mod_specweb99 if you are only
doing static content.

Greg