linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Martin Brulisauer" <martin@bruli.net>
To: Ernst Herzberg <earny@net4u.de>, Marco Colombo <marco@esi.it>
Cc: Adam Goldstein <Whitewlf@Whitewlf.net>, <linux-kernel@vger.kernel.org>
Subject: Re: Very High Load, kernel 2.4.18, apache/mysql
Date: Fri, 27 Sep 2002 10:52:41 +0200	[thread overview]
Message-ID: <3D943879.10625.35E0D4C@localhost> (raw)
In-Reply-To: <Pine.LNX.4.44.0209262035060.26363-100000@Megathlon.ESI>


Turn on extended status in your apache configuration file:
-> ExtendedStatus On
so you can see more information on what the server is
doing. The information looks like:

Current Time: Friday, 27-Sep-2002 10:48:59 CEST\x0f
Restart Time: Tuesday, 27-Aug-2002 17:42:47 CEST\x0f
Parent Server Generation: 32 \x0f
Server uptime: 30 days 17 hours 6 minutes 12 seconds\x0f
Total accesses: 256966 - Total Traffic: 1.7 GB\x0f
CPU Usage: u11.3027 s6.76172 cu14.4033 cs2.29785 - .00131% CPU 
load\x0f
.0968 requests/sec - 702 B/second - 7.1 kB/request\x0f
1 requests currently being processed, 5 idle servers 

Martin


On 26 Sep 2002, at 20:36, Marco Colombo wrote:

> On Thu, 26 Sep 2002, Ernst Herzberg wrote:
> 
> > First reconfigure your apache, with
> > 
> > MaxClients 256  # absolute minimum, maybe you have to recompile apache
> > MinSpareServers 100  # better 150 to 200
> > MaxSpareServers 200 # bring it near MaxClients
> 
> KeepAlive		On
> MaxKeepAliveRequests	1000
> 
> .TM.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 



  parent reply	other threads:[~2002-09-27  8:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0EBC45FCABFC95428EBFC3A51B368C9501AF4F@jessica.herefordshire.gov.uk>
2002-09-25 20:16 ` Very High Load, kernel 2.4.18, apache/mysql Adam Goldstein
2002-09-25 21:26   ` Roger Larsson
2002-09-26  3:03   ` Ernst Herzberg
2002-09-26 18:36     ` Marco Colombo
2002-09-26 19:27       ` Rik van Riel
2002-09-26 20:02         ` Marco Colombo
2002-09-26 20:09           ` Rik van Riel
2002-09-26 20:25         ` Ernst Herzberg
2002-09-27  8:52       ` Martin Brulisauer [this message]
2002-10-01  5:36   ` David Rees
     [not found] <3D90FD7B.9080209@wanadoo.fr>
2002-09-25  1:12 ` Adam Goldstein
2002-09-24 23:27 Adam Goldstein
2002-09-25  0:59 ` Roger Larsson
2002-09-25  1:28   ` Rik van Riel
2002-09-25  2:38     ` Adam Goldstein
2002-09-25  5:24       ` Simon Kirby
2002-09-25  6:56         ` Adam Goldstein
2002-09-25  7:20           ` Simon Kirby
2002-09-25  7:51             ` Paweł Krawczyk
2002-09-25 13:13       ` Rik van Riel
2002-09-25 22:54       ` Jose Luis Domingo Lopez
2002-09-26 17:09       ` Joachim Breuer
2002-09-26 17:16         ` Rik van Riel
2002-09-25  3:50     ` Bernd Eckenfels
2002-09-25  3:48 ` Bernd Eckenfels

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D943879.10625.35E0D4C@localhost \
    --to=martin@bruli.net \
    --cc=Whitewlf@Whitewlf.net \
    --cc=earny@net4u.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marco@esi.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).