This is the place. =) Submit a proposal for how you think PerlRun
should change, and get people to discuss it so you can settle on
something that seems good. Then submit a patch, preferably against the
CVS version.
[EMAIL PROTECTED] (Andrew Chen) wrote:
>Yeah, that sounds about right... It's
Yeah, that sounds about right... It's not at either extreme-- it doesn't
keep EVERYTHING, and it doesn't kill the Apache child to clear the memory.
I'm sure the exact directives can be thought out later.
So who do I get in touch with in order for this stuff to get looked at for
inclusion into mod
[EMAIL PROTECTED] (Andrew Chen) wrote:
>Hello all,
>
>I was involved in a discussion a few weeks ago regarding how Cobalt Group
>(www.cobaltgroup.com) could get a performance boost by running our very
>very dirty modules under PerlRun with PerlRunOnce Off and then to have a
>handler that cleaned u
Hello all,
I was involved in a discussion a few weeks ago regarding how Cobalt Group
(www.cobaltgroup.com) could get a performance boost by running our very
very dirty modules under PerlRun with PerlRunOnce Off and then to have a
handler that cleaned up between requests.
Anyway, with a lot of he
