From: Benjamin Podszun <ben@galactic-tales.de>
To: "Robin H.Johnson" <robbat2@gentoo.org>
Cc: Brian Jackson <brian@mdrx.com>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Performance once again..
Date: 12 Apr 2003 23:46:40 +0200 [thread overview]
Message-ID: <1050184000.1273.32.camel@blafasel> (raw)
In-Reply-To: <20030412204540.GA5108@cherenkov.orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 1741 bytes --]
On Sat, 2003-04-12 at 22:45, Robin H.Johnson wrote:
> On Sat, Apr 12, 2003 at 10:32:00PM +0200, Benjamin Podszun wrote:
> > The Apache-Version is the same, so is the configuration.
> > The only thing that I noticed is that one apache instance sucks up to
> > 99% CPU... It never uses less than 30% ..
> > And since this is a Compaq Server with Dual P3 1GHz and 2GB RAM I doubt
> > that this is right (tm).
> Do you use PHP (and possibly MySQL) on that machine? I saw that problem
> on my Slackware box a few months ago. I never did find the solution tho,
> as I upgraded to Apache2. I did confirm that the bug didn't occur when
> PHP wasn't being used for me. For some reason, PHP seemed to be in a
> massive loop after the page was sent, eating CPU and memory.
Uhm.. Yes, I use Apache and PHP. MySQL as well, but not on that host (3
production servers, two of them only with apache/php, both compaq as
stated above, the third only serves as DB-Server. Both Webserver have
that problem.
You upgraded to Apache2? I guess (hope?) that you don't talk about
production environments? I tried to use Apache2 with PHP twice and
wouldn't recommend it to anyone.. It's just buggy and not usable. As my
current Gentoo-Servers are.. *cough*
> A good temporary workaround is to have a little watcher shell script
> that looks for any apache processes that have been eating >80% CPU for
> the all of the last 30 seconds (I checked at 30 second intervals) and
> send a SIGKILL to them.
Well, that's an ugly hack.. Yes, thanks for the hint, but I already
thought about something like this.. And I don't think that it solves a
single problem, nor is it a suitable solution on a (I love this word)
production environment.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-12 21:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 19:09 [gentoo-dev] Performance once again Benjamin Podszun
2003-04-12 19:13 ` Jon Portnoy
2003-04-12 19:44 ` Benjamin Podszun
2003-04-12 19:54 ` Jon Portnoy
2003-04-12 20:24 ` Brian Jackson
2003-04-12 20:32 ` Benjamin Podszun
2003-04-12 20:38 ` Hasse Hagen Johansen
2003-04-12 20:44 ` Benjamin Podszun
2003-04-12 22:25 ` Martin Schlemmer
2003-04-12 22:55 ` Benjamin Podszun
2003-04-12 23:30 ` Martin Schlemmer
2003-04-13 15:46 ` Benjamin Podszun
2003-04-13 18:11 ` Martin Schlemmer
2003-04-13 21:20 ` Benjamin Podszun
2003-04-12 20:45 ` Robin H.Johnson
2003-04-12 21:46 ` Benjamin Podszun [this message]
2003-04-12 22:05 ` leahcim
2003-04-12 22:09 ` Robin H.Johnson
2003-04-12 22:17 ` Brad Laue
2003-04-12 22:35 ` Benjamin Podszun
[not found] ` <1050187146.3931.12.camel@nexus6.musikcheck.dk>
2003-04-12 22:51 ` Benjamin Podszun
2003-04-13 0:22 ` Brad Laue
2003-04-12 22:32 ` Terje Kvernes
2003-04-14 8:51 ` Václav Hůla
2003-04-14 9:03 ` Benjamin Podszun
2003-04-14 9:33 ` Paul de Vrieze
2003-04-14 12:30 ` Dar-Klajid
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=1050184000.1273.32.camel@blafasel \
--to=ben@galactic-tales.de \
--cc=brian@mdrx.com \
--cc=gentoo-dev@gentoo.org \
--cc=robbat2@gentoo.org \
/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