Return-Path: X-Original-To: apmail-httpd-users-archive@www.apache.org Delivered-To: apmail-httpd-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 13A08106DE for ; Mon, 29 Apr 2013 17:07:36 +0000 (UTC) Received: (qmail 84947 invoked by uid 500); 29 Apr 2013 17:07:32 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 84917 invoked by uid 500); 29 Apr 2013 17:07:32 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 84906 invoked by uid 99); 29 Apr 2013 17:07:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Apr 2013 17:07:32 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kongfranon@gmail.com designates 209.85.210.178 as permitted sender) Received: from [209.85.210.178] (HELO mail-ia0-f178.google.com) (209.85.210.178) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Apr 2013 17:07:26 +0000 Received: by mail-ia0-f178.google.com with SMTP id j38so5692478iad.37 for ; Mon, 29 Apr 2013 10:07:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=9J7P+5bgETsPgnYxQ7lNp47qNLfo5uVy0JxS0oaQ6FY=; b=KY1BVcGlYHJTXqriwSqsbqUQBTEP5gw4XueDIHWM1l2oJCDSPFbiudQRg28tBD7cad 6mI+nPDbm5HeLRL8cSd0WdRk41/R/VPaUV/i0sinbBb4FSRFn2RHk0vYGcSr+guSEpZQ f1gRBPeazTjfUGiSHisoNbGcU/rYJCkf22/fejUuVsRTJdiFI7Reun3QyOQ6mMH+Ctdx GSpsr7zGyqBiv6L2b+onhwdhcmASF0Nqf9HG88e92I5p/1rHKevWGjlaAatI1qmcPy5j ysp2/u8THDHznz1nAt/xeu+Isw94EJfPxy9dpVJLEy7uqIPTUhPf9/JCeZTCD6f4B9TO xE3g== MIME-Version: 1.0 X-Received: by 10.50.47.10 with SMTP id z10mr1506197igm.15.1367255226139; Mon, 29 Apr 2013 10:07:06 -0700 (PDT) Received: by 10.64.44.40 with HTTP; Mon, 29 Apr 2013 10:07:05 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Apr 2013 13:07:05 -0400 Message-ID: From: Mike Franon To: users@httpd.apache.org Content-Type: multipart/alternative; boundary=089e013d08d4124cba04db82eae7 X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] apache 2.4 with MPM Event recommend config --089e013d08d4124cba04db82eae7 Content-Type: text/plain; charset=ISO-8859-1 Thanks for the info so for 2.4 it would be very similar? For us we get anywhere form 10 RPS to 20 RPS on average and during peak periods or sales/promos we get upwards of 150-200 RPS Thanks On Fri, Apr 26, 2013 at 11:50 AM, Tom Evans wrote: > On Fri, Apr 26, 2013 at 3:41 PM, Mike Franon wrote: > > Hi, > > > > I recently moved to apache 2.4.4 with php-fpm, mod_fastcgi, and MPM > Event. > > > > I was curious what values do I need to change to optimize apache? > > > > I remember in 2.4 prefork I had to change several like MaxClients and > > MaxRequestsPerChild > > > > > > > > The server I am running it on has 30 GB Ram, and 8 Cores > > > > > > I know usually the defaults are not great out of the box and curious if > you > > have any recommendations to get the best performance possible for apache > 2.4 > > > > Thanks > > > > > > What are your average and max concurrent requests per second that you > want to achieve? Simply tune to that - you will find apache with event > MPM (and without language interpreters embedded in httpd, eg using > php-fcgi) does not use much memory or CPU at all. > > Eg, for our moderately loaded proxies, which use apache 2.2 with event > MPM, we have average of around 50 RPS (per proxy, there are a few of > them), with peaks of around 500 RPS. We configure the server: > > StartServers 8 > MaxClients 1024 > MinSpareThreads 128 > MaxSpareThreads 768 > ThreadsPerChild 64 > MaxRequestsPerChild 0 > > So we start 8 servers, each with 64 threads, giving us 512 request > slots immediately. Whenever there are less than 128 spare slots, we > start an extra server, up to a maximum of 1024 slots (16 servers), and > we reap a server whenever there are more than 768 spare slots. We also > trust that Apache without interpreters does not leak RAM, so don't > bother reaping servers after a certain number of handled requests. > > Our normal and peak usage fits in to the slots started initially, with > scope to grow if needed. These servers only serve static files off > disk, or proxy requests to backend servers. Memory usage and load > remain steady on each proxy, apache uses less than 1 GB of RAM, load > average has never been above 1. > > Hope that helps > > Cheers > > Tom > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org > For additional commands, e-mail: users-help@httpd.apache.org > > --089e013d08d4124cba04db82eae7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thanks for the info so for 2.4 it would be very similar?
For us we get anywhere form 10 RPS to 20 RPS on ave= rage and during peak periods or sales/promos we get upwards of 150-200 RPS<= /div>

Thanks


On Fri, Apr 26, 2013 at 11:50 AM, Tom = Evans <tevans.uk@googlemail.com> wrote:
On F= ri, Apr 26, 2013 at 3:41 PM, Mike Franon <kongfranon@gmail.com> wrote:
> Hi,
>
> I recently moved to apache 2.4.4 with php-fpm, mod_fastcgi, and MPM Ev= ent.
>
> I was curious what values do I need to change to optimize apache?
>
> I remember in 2.4 prefork I had to change several like MaxClients and<= br> > MaxRequestsPerChild
>
>
>
> The server I am running it on has 30 GB Ram, and 8 Cores
>
>
> I know usually the defaults are not great out of the box and curious i= f you
> have any recommendations to get the best performance possible for apac= he 2.4
>
> Thanks
>
>

What are your average and max concurrent requests per second th= at you
want to achieve? Simply tune to that - you will find apache with event
MPM (and without language interpreters embedded in httpd, eg using
php-fcgi) does not use much memory or CPU at all.

Eg, for our moderately loaded proxies, which use apache 2.2 with event
MPM, we have average of around 50 RPS (per proxy, there are a few of
them), with peaks of around 500 RPS. We configure the server:

=A0 =A0 StartServers 8
=A0 =A0 MaxClients 1024
=A0 =A0 MinSpareThreads 128
=A0 =A0 MaxSpareThreads 768
=A0 =A0 ThreadsPerChild 64
=A0 =A0 MaxRequestsPerChild 0

So we start 8 servers, each with 64 threads, giving us 512 request
slots immediately. Whenever there are less than 128 spare slots, we
start an extra server, up to a maximum of 1024 slots (16 servers), and
we reap a server whenever there are more than 768 spare slots. We also
trust that Apache without interpreters does not leak RAM, so don't
bother reaping servers after a certain number of handled requests.

Our normal and peak usage fits in to the slots started initially, with
scope to grow if needed. These servers only serve static files off
disk, or proxy requests to backend servers. Memory usage and load
remain steady on each proxy, apache uses less than 1 GB of RAM, load
average has never been above 1.

Hope that helps

Cheers

Tom

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


--089e013d08d4124cba04db82eae7--