[ Sorry for accidentally spamming people on the
list. I was ticked off by this "benchmark",
and accidentally forgot to clean up the reply
names. I won't let it happen again :( ]
Matt Sergeant <[EMAIL PROTECTED]> writes:
> On Thu, 21 Dec 2000, Ken Williams wrote:
>
> > Well then, why doesn't somebody just make an Apache directive to control how
> > hits are divvied out to the children? Something like
> >
> > NextChild most-recent
> > NextChild least-recent
> > NextChild (blah...)
> >
> > but more well-considered in name. Not sure whether a config directive
> > would do it, or whether it would have to be a startup command-line
> > switch. Or maybe a directive that can only happen in a startup config
> > file, not a .htaccess file.
>
> Probably nobody wants to do it because Apache 2.0 fixes this "bug".
>
KeepAlive On
:)
All kidding aside, the problem with modperl is memory consumption,
and to use modperl seriously, you currently have to code around
that (preloading commonly used modules like CGI, or running it in
a frontend/backend config similar to FastCGI.) FastCGI and modperl
are fundamentally different technologies. Both have the ability
to accelerate CGI scripts; however, modperl can do quite a bit
more than that.
Claimed benchmarks that are designed to exploit this memory issue
are quite silly, especially when the actual results are never
revealed. It's overzealous advocacy or FUD, depending on which
side of the fence you are sitting on.
--
Joe Schaefer
