Hi Dan, We run our C::A apps under a mix of mod_perl, persistent perl and cgi, depending on what they need to do and how often. Some of our apps have a substantial startup because of database initialisation under Class::DBI, so we run those under persistent perl rather than cgi. The think I like about persistent perl is that it is pretty easy to configure how long you want a process to stay alive, how many processes you want to run and how you want to share memory amongst processes. The apps we have running under persistent perl are probably the most active on our servers, with well over 100K requests every day.
Regards, David Dan Horne wrote: >Hi All > >I've got a C::A app that runs pretty slow as a CGI, but runs nice and fast >under mod_perl. My problem is that once I add all the various modules to >startup.pl, the httpd processes consume a lot of memory. > >So I'm looking for an alternative mod_perl, and the two options seem to be >FastCGI and Persistent Perl. Is there any reason to use one over the other? >Have anyone used both, and has come to a conclusion about which is best for >a C::A app? > >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] > > > > >
--------------------------------------------------------------------- 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]
