From: Benjamin Podszun <ben@galactic-tales.de>
To: "Robin H.Johnson" <robbat2@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Performance Apache/PHP / PHP-Problem
Date: 16 Apr 2003 13:13:19 +0200 [thread overview]
Message-ID: <1050491599.1161.12.camel@blafasel> (raw)
In-Reply-To: <20030416092910.GA30695@cherenkov.orbis-terrarum.net>
[-- Attachment #1: Type: text/plain, Size: 2725 bytes --]
Thanks.. Stupid me, I should've formatted it before I ask for help.
But I'm really quite annoyed already.. I cannot find any difference
between the Debian Installation that worked for about a year and this
Gentoo 1.4 . I'm sure I made a mistake somewhere, but I've no idea where
to start the search.
KeepAlive is already disabled.
The "W" states that it is currently responding to a request, right? I
used KeepAlive before, but a keepalive-State would be a "K" in the
"M"-Column.
PHP connections can only be persistant for Databases, afaik?
However: We don't use persistant connections and I just disabled them
completely.
No ideas what else I could turn off right now. :(
On Wed, 2003-04-16 at 11:29, Robin H.Johnson wrote:
> On Wed, Apr 16, 2003 at 10:57:09AM +0200, Benjamin Podszun wrote:
> > I posted my Apache problems before and I think I found the root cause
> > now. I have a nntp2web-gateway as forum and the nntp-server regularly
> > reaches a high load because of some other applications.
> > The server still accepts connections, but feeds more or less a "wait a
> > moment" to my webserver..
>
> > First problem for me: Gentoo's mod_php isn't build with
> > --enable-memory-limit. I needed that to solve some of my performance
> > problems and I think it should be used by default, since one can set the
> > limit in the php.ini.
> Ok, I'll at this in shortly.
>
> > Second problem: I seem to miss something here.. My php-scripts won't
> > stop receiving data in spite of my self-made memory-limit-aware mod_php.
> > I get funny thinks like this with apachectl fullstatus:
> > Srv PID Acc M CPU SS Req Conn Child Slot Client VHost Request
> > 0-0 24732 0/9710/9710 W 255.39 48435 0 0.0 12.94 12.94 217.82.173.211
> > galactic-tales.4players.de GET /nntp2web/thread.php?group=rpg
> > HTTP/1.1
> You have misread the columns.
>
> Align the columns better or look at the web version "http://localhost/server-status" in a table capable browser.
> Srv PID Acc M CPU SS Req Conn Child Slot Client VHost ...
> 0-0 24732 0/9710/9710 W 255.39 48435 0 0.0 12.94 12.94 217.82.173.211 galactic-tales.4players.de ...
>
> The ~50 you see is NOT the size, it's the time in seconds since the last
> request. The 'W' shows that the request is still open, so that IS a
> serious issue. I would turn off keepalives + persistant connections in
> apache/php totally. There is minimal performance gain with them in PHP
> anyway. The '12.94Mb' for the Child column is how much that Apache child
> process has transfered over its lifetime.
> 9170 connections and 12.94Mb is quite low traffic.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-04-16 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 8:57 [gentoo-dev] Performance Apache/PHP / PHP-Problem Benjamin Podszun
2003-04-16 9:29 ` Robin H.Johnson
2003-04-16 11:13 ` Benjamin Podszun [this message]
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=1050491599.1161.12.camel@blafasel \
--to=ben@galactic-tales.de \
--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