Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (asf.osuosl.org: domain of jslive@gmail.com designates
 66.249.92.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=pM23xQJrZlC01fNc/1vgXXOURqdEjsFANsgSdQfSgfR8cy/JuOUrirPL9vAAJPL+xtULgbmzG8sTFGawVm8AfG/i7DTDa0TqKiaLVEL8HJI3yEoOfTYppofPFrHAz3kmy5Yp4s8e2JtygX7XcZPijzq6sLXk0C+RQOx7FasbcoA=
Message-ID: <e498c1660607181436w5a2a674ar344b135ba0e9e433@mail.gmail.com>
Date: Tue, 18 Jul 2006 17:36:18 -0400
From: "Joshua Slive" <joshua@slive.ca>
Sender: jslive@gmail.com
To: users@httpd.apache.org
In-Reply-To: <44BCFAE1.9030803@fenix.cz>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44BCFAE1.9030803@fenix.cz>
Subject: Re: [users@httpd] performance considerations (looong)

On 7/18/06, Pavel Stratil <pavel.stratil-jun@fenix.cz> wrote:
> Hi all!
>
> I have an older machine with no real funds to upgrade hw and growing
> traffic. Apache eats most of the resources, before some basic config
> tweaking enough to take the machine down (now average cpu load 35% (peak
> 70), avg mem usage 85% (peak 100)). The biggest issue is memory and
> processor load and also traffic (about 1 TB/month). To be able to
> further optimize the performance, i'd rely on your experiences. I ask a
> lot at once so please dont be afraid of partial answers:-)

As a general comment, this question is far too broad to get a decent
response on a forum like this.  This is more like something you would
drop in the hands of a consultant.

If you want help from the list, I'd break your issue into small,
specific questions.  Then there is a better hope of getting
constructive responses.

To hit a few of your specific questions:

- DYNAMIC_MODULE_LIMIT isn't going to help you in any substantial way.
 I'd just ignore it.

- Caching is documented here:
http://httpd.apache.org/docs/2.2/caching.html
You should really use 2.2, and you should start with mod_disk_cache as
the most generally useful solution.  I believe that, in the case of
mod_deflate-processed content, the cache will wind up storing both a
deflated and a non-deflated variant since both will be requested by
clients.

Caching could help you alot, but your dynamic content needs to be
carefully structured to allow for caching.  If high CPU usage is the
problem, you should spend most of your time optimizing your php
scripts.  Any change you make in apache will just be noise compared to
that.  For memory, your idea of splitting into dynamic and static
servers is good.  Both servers should be stripped to the bare minimum
modules.

Joshua.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org