Hi there, On Fri, 19 Mar 2004, Jay Hannah wrote:
> We're playing with a large OO Perl 5 project under mod_perl. :( > Apache/2.0.48 (Unix) mod_perl/1.99_13 Perl/v5.8.3 mod_ssl/2.0.48 OpenSSL/0.9.7d > Linux 2.4.21-192-default #1 i686 i686 i386 GNU/Linux > (SuSe) That's an old kernel, I'd think it worth upgrading. > should there be no perl processes running at all because perl is embedded in httpd? Yes and no. If you are launching Perl scripts via CGI for example, you'll still be running Perl interpreters separately. Don't do it. :) > Just looking for super-rough ballparks of where we should be setting > our expectations. Right now we're seeing the first behavior, which > makes me think we're doing something wrong...? You might just be misreading what the tools tell you. Are you using 'top' to see the processes? Older versions will tell you that each thread is consuming memory, which isn't true. Newer versions will know the difference between processes and threads. How much RAM do you have anyway? There's a lot of useful information about performance tuning in the mod_perl Guide, including suggestions for things like proxy setups where a few mod_perl servers do the heavy Perl processing and a lot of small non-mod_perl servers do most of the communicating with clients. Broadly speaking you will have one mod_perl process per simultaneous client connection if you have only a mod_perl Apache running and yes, that can get a bit heavy on memory if you have a lot of simultaneous mod_perl clients. 73, Ged. -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
