Child Process Expiration ( Was RE: Memory Usage)

[Tom Harper <to...@auctionet.com>]

Hi Folks--

This may be slightly off topic, but I suppose adds to the 
prior discussion-- G.W. Haywood (i think?) said that he set
child process expiration at 100 hits-- this seems small to
me, mostly because the 1.3.9 apache distribution notes 
(which claims that 10,000 is high), and partly because 
throttling at 1000 has seemed to work (so far) for me...

was wondering what other folks set their child process 
expiration at for best performance with mod-perl (and 
why) ?

Any wisdom would be helpful,

Tom


At 06:22 PM 11/7/00 -0600, Christian Gilmore wrote:
>Find attached the rotatelogs.pl script. My experience is that killing off
>children after so much usage is a GoodThing (tm). So long as the parent
>remains at a stable size, things should go ok.
>
>Regards,
>Christian
>
>> -----Original Message-----
>> From: root@email.rentzone.org
>> [mailto:root@email.rentzone.org]On Behalf
>> Of Buddy Lee Haystack
>> Sent: Tuesday, November 07, 2000 3:27 PM
>> To: Christian Gilmore
>> Cc: 'G.W. Haywood'; 'mod_perl list'
>> Subject: Re: Memory Usage
>>
>>
>> Thanks Christian!
>>
>> Scripts would be nice.;-)
>>
>> I take it you've used DSO much more than I have, so I'm
>> interested in any information in addition to that provided by
>> the kind "G.W. Haywood" to the following:
>>
>> "What concerns me even more is the fact that I have Apache
>> restart child processes after they each serve 100 requests
>> [MaxRequestsPerChild 100] it's a RedHat default that is
>> supposed to reduce memory leaks, but with mod_perl & DSO it
>> may actually have the opposite effect. I can easily increase
>> the value, or remove it altogether. Any recommendations?"
>>
>>
>> Christian Gilmore wrote:
>> >
>> > > I'm leaning along the lines of just killing the
>> > > process, rotating the logs, and restarting it. It should take
>> > > no more than 5 seconds once a week a 4:00am.
>> >
>> > This is exactly what I do, except I have it scripted. The
>> downside is that
>> > your service is unavailable for a few seconds (maybe more
>> depending upon
>> > the length of time it takes for the parent to wipe out all the old
>> > children). I'd be happy to share the script, provided my
>> boss doesn't
>> > mind. :)
>> >
>> > Regards,
>> > Christian
>>
>> --
>> BLH
>> www.RentZone.org
>>
>
>
>Attachment Converted: "d:\eudora\attach\rotatelogs.pl"
>

Re: Child Process Expiration ( Was RE: Memory Usage)

[Perrin Harkins <pe...@primenet.com>]

On Mon, 13 Nov 2000, Tom Harper wrote:
> was wondering what other folks set their child process 
> expiration at for best performance with mod-perl (and 
> why) ?

I set it to 0 and use Apache::SizeLimit.  No point in killing a process
that isn't too large just because it served x number of requests.
- Perrin

Re: Child Process Expiration ( Was RE: Memory Usage)

["G.W. Haywood" <ge...@www.jubileegroup.co.uk>]

Hi there,

On Mon, 13 Nov 2000, Tom Harper wrote:

> G.W. Haywood (i think?) said that he set child process expiration at
> 100 hits-- this seems small to me,

Yes, it was he.

He also said that most people think that's rather low and set it higher...

73,
Ged.