RE: HTTP server tuning

The HTTP server job.  Put it in a pool with the memory it can hog.  You
can have a single drive system at 40% so what really matters is the
configuration.  40% utilization is good but you get better performance
from 4 drives vs. less.  Also if you do not need the protection, turn
off RAID-5.  The 170 controllers were not all that powerful and the
drive not all that fast.  As someone else suggested, check which pool
the apache server is running in and make sure that pool has plenty of
memory and not paging.  Make sure the machine and base pool is not
paging too much too.  That effects the whole system.

Once you know that you do not have a memory or DASD constraints, then
check CPU usage.  Is the apache server pegging the CPU?  What is your
CPW or model number?  9406-170/2289,2290,2291...


Christopher Bipes
Information Services Director
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Trevor Perry
Sent: Wednesday, May 31, 2006 8:37 AM
To: Midrange Systems Technical Discussion
Subject: Re: HTTP server tuning

Chris,

It is a 170 with 784MB and the DASD is plenty (cannot remember the
details) - only 40% used. It is running a green ERP application where
the data for the HTML application is stored.

So, what do you mean by give "it" all the memory you can afford? By
"it", do you mean the 170? the pool?

We are planning an upgrade to a 520, and we will soon benchmark
performance of the HTML application on that platform. Does anyone know
of the expected performance increase of the application if we go from
170 to 600CPW?