On 24/05/2011 06:23, Joshua Miller wrote: > On Mon, May 23, 2011 at 11:15 PM, gvim<gvi...@gmail.com> wrote: > > "isn't there a huge startup penalty..." Not if you're using FastCGI, > PSGI + something like FastCGI or mod_perl, mod_perl, Starman or any > other persistent perl thing. In those cases, it loads and compiles > once, and subsequent hits go to the compiled perl bytecode (more or > less). It's actually better and faster to have everything loaded at > first in these, so that memory is shared (COW for mod_perl under > linux). Under plain old bare-bones CGI, yes, there is a startup > penalty on every hit. >
Whilst a FastCGI solution improves startup time it doesn't address the memory footprint. I'm comparing deploying an app with CGI::Application vs. CGI with separate Perl scripts on a VM with a modest amount of mempory. From the what I'm learning about CGI::Application it seems that the memory footprint will skyrocket if your codebase has, say, 15 Perl scripts each containing over 300 lines of code as you now have 15 x 300 lines of code running instead of 300, no? gvim ##### CGI::Application community mailing list ################ ## ## ## To unsubscribe, or change your message delivery options, ## ## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp ## ## ## ## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ## ## Wiki: http://cgiapp.erlbaum.net/ ## ## ## ################################################################
