Dan Horne wrote:
> Hi Richard
> 
>>From: Richard Dice 
>>Dan,
>>
>>I expect that they're all going to experience the same memory situation.
>>They
>>all operation on basically the same idea.  (Though if anyone out there has
>>a
>>different perspective then I'd love to hear it.  mod_perl is the only one
>>of
>>them I have extensive experience with.)
> 
> 
> Thanks for the reply, Richard. I was trying to think of a way to avoid
> setting up a separate Apache install to serve static pages that are
> generated by the mod_perl backend. I was hoping that Persistent Perl or
> FastCGI would be lighter, since I don't need mod_perl for every request.
> They may still be, so I'll give it a go.

In my eyes they are about the same. All of them involve having a
separate daemon running that the front end apache (or whatever) can send
dynamic requests to. Setting up 2 instances of apache is dead simple and
you don't even need 2 installations. Just use the same binary with
different config files.

>>Don't forget that, when you look at your Apache children's memory usage,
>>much of
>>the memory-bloat is shared so it's not really as bad as it looks at first.
> 
> 
> For some reason that I can't fathom, whenever I look at the memory used by
> the httpd processes, very little is shared. I can't figure this out - I make
> sure everything defined in the startup script, prepare my connections etc
> ... basically follow the setup in http://modperlbook.org/

What OS are you using? Recent versions of linux (2.4-2.6) have problems
with reporting shared memory. This is being fixed but unless you've
patched your kernel you wont see how much memory processes are sharing.


You can read more here:
http://www.gossamer-threads.com/lists/modperl/modperl/78318?search_string=gtop%20linux%20shared;#78318


-- 
Michael Peters
Developer
Plus Three, LP


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/[email protected]/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to