Re: [cgiapp] CAP::Apache and CAP::Session

[Cees Hek <suppressed>]

On Tue, 16 Nov 2004 17:10:08 -0500, Jesse Erlbaum <suppressed> wrote:
> Performance benefits over Apache::Registry seem marginal when you
> consider the total request time (network transit, database access, etc.)
> OTOH, functionality takes a hit, as you are now seeing.

Also, if the only part of mod_perl you are using is Apache::Registry
for your perl scripts (or just writing content Handlers), then might I
recommend PersistentPerl.  This allows your apache processes to remain
small (mod_perl adds significantly to the memory requirements of
apache), and also gives you the ability to group your CGI scripts into
different process groups, giving you greater control over memory
resource usage.

I haven't actually done a speed comparison between perperl and
mod_perl, but I would guess they are minor (mod_perl probably being
slightly faster).

Don't get me wrong, I think mod_perl is a great app and I have been
using it for years, but unless you really need to dig into the guts of
Apache to build your app, then there are other alternatives.

Cheers,

-- 
Cees Hek

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