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. > > 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/ Thanks Dan --------------------------------------------------------------------- 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]
