public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Benjamin Podszun <ben@galactic-tales.de>
To: brad@brad-x.com
Cc: "Robin H.Johnson" <robbat2@gentoo.org>,
	Brian Jackson <brian@mdrx.com>,
	 gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Performance once again..
Date: 13 Apr 2003 00:35:06 +0200	[thread overview]
Message-ID: <1050186906.1280.40.camel@blafasel> (raw)
In-Reply-To: <1050185822.32740.2.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]

On Sun, 2003-04-13 at 00:17, Brad Laue wrote:
> On Sat, 2003-04-12 at 17:46, Benjamin Podszun wrote:
> 
> > 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*
> 
> Hardware configuration? Amount of RAM? Number of CPU's? What specific
> revision of gentoo-sources? Have you tried vanilla-sources or alan cox's
> patchset? What configuration options had you given the Debian kernel and
> do they differ from those you gave to Gentoo's kernel?

Uhm.. I did post my hardware, but maybe it wasn't clear enough in all my
messages.
Compaq-Server, 2 1GHz CPUs, 2GB RAM, no special hardware, apart from
Smart Arrays..
Vanilla-sources 2.4.20

Debian:
vanilla 2.4.18, built with the "normal" way, no deb-package

> Have you tried 2.4.18 under Gentoo to see if it solves your problems?

Yes, no difference

> This isn't a matter of Debian working and Gentoo not working; there's a
> configuration difference between the two, that's all.

Yes, I don't doubt it. But I copied the php.ini, apache-config-files and
I don't see the difference. The only thing I see is that apache sucks up
to 99% CPU (I don't know if it was the same on the Debian system,
honestly) and the server stops responding to any requests while the load
drops to ~ 0 ..

Ben

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-04-12 22:36 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
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 [this message]
     [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=1050186906.1280.40.camel@blafasel \
    --to=ben@galactic-tales.de \
    --cc=brad@brad-x.com \
    --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