On 23 Aug 2006, at 21:20, Jonathan wrote:
First off, Jonathan T and are running the same setup and compile
options. I believe its just the stock apache 2.0 port off freebsd.
Correct.
philip has more memory sharing than me, but not as much as
Jonathan T.
Sorry for my ignorance, but does the line
www 60645 0.0 5.8 73068 60504 ?? S 8:25PM 0:00.00 /usr/
local/sbin/httpd
mean that 73068 - 60504 = 12564 is shared (at least according to ps)?
Is this normal? Given that Philip has less sharing than less, is this
the most I can hope for?
have either of you profiled the memory sharing on another
platform? ( ie, local osx or linux box )
I've just tried OS X, see other response. Apache 1.3 though
unfortunately, so probably useless in this discussion.
root 60641 22.6 5.8 73068 60492 ?? Ss 8:25PM 0:02.08
73MB thats nothing for mod_perl + php its fairly typical actually.
i'm going to patch docs to say that. the mp docs + mp book + devel
cookbook are a bit misleading- they suggest that 12MB of parent +
5mb child is typical. its really not.
Those are the only figures I've seen, other than those in this
thread, and they are a lot lower than those quoted in this thread so
they are clearly misleading.
These numbers seem really high to me. I have both mod_perl and
mod_php installed and am running two perl sites and four php sites.
You should separate these out to separate apache instances....
unless you've a good
reason not to.
unless you need some random apache module for php permissions, i'd
strongly suggest removing mod_php altogether. run php via fastcgi+
eaccelerator, and serviced by nginx or lighttpd (just set a cronjob
to restart lighttpd at 3am every morning, its got a nasty memory
leak right now). you'll see a gigantic performance boost- both in
mod_perl and on your php sites.
I looked at lighttpd a few days ago but wasn't overly impressed.
There seems to be a lot of people with stability issues (as your
"restart it every day" comment proves) and in my completely
unscientific tests images seemed to served visibly faster by a fat
Apache than by lighty which greatly surprised me.
The box in question is hopefully going to see a significant traffic
increase soon to one of the Perl apps so I am going to have to go to
some sort of proxy set up soon. Maybe there's something in running
three Apaches as Philip suggested (a light front end, one for
mod_perl and one for PHP)?
Cheers
Jonathan
