On Wed, Apr 25, 2001 at 07:19:25PM +0800, Stas Bekman wrote:
> > if I set say MaxRequestsPerChild 1 ??
>
> Not if you preload your scripts at the server startup. But then you pay
> the price of the time to spawn a new process, which has a very little
> overhead under low load since Apache prefor
On Wed, 25 Apr 2001 [EMAIL PROTECTED] wrote:
In a different thread [EMAIL PROTECTED] said:
> I have read the "guide" cover to cover long ago :)
In the other thread [EMAIL PROTECTED] has asked:
> Not exactly sure how to preload these scripts. I have the following
the two events contrudict and
Thanks. I think that is what I really need :)
On Wed, Apr 25, 2001 at 08:19:21PM +0800, Stas Bekman wrote:
> the two events contrudict and lead to the need to re-read the guide, and
> especially this section:
> http://perl.apache.org/guide/performance.html#Preloading_Registry_Scripts_at_S
>
> :
On Wed, Apr 25, 2001 at 12:10:01PM +0100, G.W. Haywood wrote:
> Hi there,
>
> On Wed, 25 Apr 2001 [EMAIL PROTECTED] wrote:
>
> > like to know whether there is a compilation overhead if I set say
> > MaxRequestsPerChild 1 ??
>
> http://perl.apache.org/guide
I have read the "guide" cover to cove
Hi there,
On Wed, 25 Apr 2001 [EMAIL PROTECTED] wrote:
> like to know whether there is a compilation overhead if I set say
> MaxRequestsPerChild 1 ??
http://perl.apache.org/guide
> disk data ransfer rate will be order of magnitude less than if the
> script were to remain in the memory all the
On Wed, 25 Apr 2001 [EMAIL PROTECTED] wrote:
> I recently began to experience many lingering
> mod_perl processes which slow down my tcp connection.
>
> I use Apache::Registry for all my mod_perl need.
> Not the "real" handler.
>
> The practical solution I found was to cut down the
> number MaxRe
I recently began to experience many lingering
mod_perl processes which slow down my tcp connection.
I use Apache::Registry for all my mod_perl need.
Not the "real" handler.
The practical solution I found was to cut down the
number MaxRequestPerChild and kill off the processes
after a few reques
