httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dean Gaudet <>
Subject Re: apache and threading (was Re:
Date Mon, 07 Jul 1997 02:35:32 GMT
I took another look, in case I was hallucinating last time I checked
this server.  It's averaging 100k unshared per child right now (based
on ps -max which displays the number of shared pages).  Task gunk takes
about 12k on linux, and so accounting 112k per task I get about 30Mb.
The system reports 38Mb of RAM in use (non-disk page).  So it checks out.

Incidentally this server and its twin run hourly restarts and the parents
have been going for over 2.7 million seconds, almost a month!

Anyone know how to get the same data from a solaris box?  I haven't seen
a method of determining shared pages.

I guess I need to rethink my attitude towards threads if linux is the only
one that somehow manages to be this aggressive.  Or perhaps we're doing
something silly that causes unsharing on the other systems.


On Sun, 6 Jul 1997, Marc Slemko wrote:

> On Sun, 6 Jul 1997, Dean Gaudet wrote:
> > Apache as it is will not benefit as much from threading as people are
> > hoping.
> > 
> > Consider memory usage.  After a fork(), what actually has to be
> > copied/unshared?  Pretty much nothing.  We don't dink with the pconf pool
> > used to hold the config info, we dink with a few globals.  We create
> > new pools for each request.  So pretty much everything up to fork time
> > is shared between all children.  I see this now, on a busy linux server
> > I see children running with 80k unshared data, and 770k shared.
> I don't see that under FreeBSD.
> On a 64 meg server, I can only hit a couple of hundred children before
> running out of memory.  Using your numbers, 500 shouldn't be a problem.  I
> didn't think Linux was that much better than FreeBSD at sharing...

View raw message