On Aug 23, 2006, at 3:51 PM, Philip M. Gollucci wrote:
load nothing, except maybe Apache::SizeLimit
...
I'll try that tonight
I'm betting that top/ps are going to be off and the RUSAGE() will
be correct
I'm not convinced that they report Copy-on-Write pages correctly
i've been profiling with top/ps , RUSAGE (BSD:Resource), and GTOP.
all 3 give me waaay different numbers. off by 10s of mbs each.
The low amount of shared memory on all these setups makes me wonder
though.
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.
Philip is running apache2.2 and has this flag on his compile that we
do not "-D APR_USE_PTHREAD_SERIALIZE"
my osx has that flag, freebsd does not , and osx is sharing 2x the
memory as freebsd.
philip has more memory sharing than me, but not as much as Jonathan T.
have either of you profiled the memory sharing on another platform?
( ie, local osx or linux box )
i need to set up a spare box tonight and see how this code operates
on debian.
from what i can tell , something is definitely broken on freebsd.
Either the memory is sharing and the bsd tools are not reporting it
correctly (entirely plausible. i can't get a consistent answer from
any method ), or something in the way apache/perl is built is causing
the memory to not share as much as it could/should.
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.
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.
