linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Rees <dbr@greenhydrant.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Very High Load, kernel 2.4.18, apache/mysql
Date: Mon, 30 Sep 2002 22:36:49 -0700	[thread overview]
Message-ID: <20020930223649.A20225@greenhydrant.com> (raw)
In-Reply-To: <B7E52DA4-D0C3-11D6-8C5C-000502C90EA3@Whitewlf.net>; from Whitewlf@Whitewlf.net on Wed, Sep 25, 2002 at 04:16:47PM -0400

I can second the PHPA recommendation.  Since you appear to be CPU bound
doing a lot of processing in httpd, anything you can do to speed them up
will help.  PHPA showed significant performance increases in my tests.

-Dave

On Wed, Sep 25, 2002 at 04:16:47PM -0400, Adam Goldstein wrote:
> During my investigation of php accelerator (which we put off before 
> thinking it would be better to stabilize the server first) I came 
> across a small blurb about php 4.1.2 (which we use) and mysql.
> 
> http://www.php-accelerator.co.uk/faq.php#segv2
> 
> Apparently this is how the site is written in some places, and it 
> causes instability in the php portion of the apache process. We are 
> fixing this now. Also, with the nodiratime, noatime, ext2 combination, 
> the load has decreased a little, but, not very much. It has still 
> reached >25 load when apache processes reached 120 (112 active 
> according to server-status) and page loads come to near dead stop... 
> segfaults still exist, even with fixed mysql connection calls. :(      
> 1-4/min under present  25+ load.
> 
> As for the syslog, unfort. almost every entry was marked async. I 
> changed an auth log entry but messages was already async. I left 
> kernel.errors sync, as It never really logs.
> 
> On Wednesday, September 25, 2002, at 04:55 AM, Randal, Phil wrote:
> 
> > Have you tried using PHP Accelerator?
> >
> > It's the only free PHP Cache which has survived my testing,
> > and should certainly reduce your CPU load.

  parent reply	other threads:[~2002-10-01  5:31 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 ` 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
2002-10-01  5:36   ` David Rees [this message]
     [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=20020930223649.A20225@greenhydrant.com \
    --to=dbr@greenhydrant.com \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Very High Load, kernel 2.4.18, apache/mysql' \
    /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

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).