From: Benjamin Podszun <ben@galactic-tales.de>
To: Brian Jackson <brian@mdrx.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Performance once again..
Date: 12 Apr 2003 22:32:00 +0200 [thread overview]
Message-ID: <1050179520.1274.24.camel@blafasel> (raw)
In-Reply-To: <200304121524.19816.brian@mdrx.com>
[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]
What kind of Infos?
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).
Any new insights?
On Sat, 2003-04-12 at 22:24, Brian Jackson wrote:
> I think I've got to agree with Jon on this one, without more info, it looks
> like an Apache/Apache config issue.
>
> --Brian
>
> On Saturday 12 April 2003 02:09 pm, Benjamin Podszun wrote:
> > Hi there.
> > I switched to Gentoo on two of my servers recently. Before that I used
> > Debian stable with a 2.4.18-Kernel.
> > Right now the machines are nearly useless. They should serve lots of
> > pages, but every ~24h everything freezes without any load on the
> > machines.. The load drops to 0.01 and nothing is delivered.
> > Only a restart of apache resets this timeframe again.
> > Well, after searching for a solution for about 3-4 days I'm already in
> > the mood to wipe Gentoo, install Debian again and stay with Gentoo for
> > Desktop only..
> > If anyone has any suggestions I'd be glad to give them a try, but I
> > cannot afford to have two systems down on a regular basis for more than
> > 2-3 days..
> >
> > I installed 1.4, used the 2.4.20 vanilla-kernel and I installed nothing
> > special but exim and apache/php.
> > All of them use the most current ebuilds in the x86 portage-tree.
> > I wonder if this is related to the problems someone pointed out with the
> > select() performance? But it would be a vanilla-problem then?
> >
> > TIA for any suggestions,
> > Ben
>
>
> --
> gentoo-dev@gentoo.org mailing list
>
[-- 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 20:33 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 [this message]
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
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=1050179520.1274.24.camel@blafasel \
--to=ben@galactic-tales.de \
--cc=brian@mdrx.com \
--cc=gentoo-dev@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