In users Digest 25 Nov 2009, Issue 3715, Peter N. Lewis wrote:
> Clearly, no one has any particularly helpful suggestions on what to do
> differently.
>
> Apache, even under relatively light load, swallowed up 700+MB over two days.
>
> So the only path forward I can see is to restart apache fairly
Clearly, no one has any particularly helpful suggestions on what to do
differently.
Apache, even under relatively light load, swallowed up 700+MB over two days.
So the only path forward I can see is to restart apache fairly regularly and
delve in to switching to nginx.
Thanks to those of you w
On 20/11/2009, at 18:21 , Nick Kew wrote:
> On 20 Nov 2009, at 09:59, Peter N Lewis wrote:
>
>> On 20/11/2009, at 17:29 , André Warnier wrote:
>>
>>> Peter N Lewis wrote:
I am having a serious problem with my site running out of memory. apache
is leaking memory/processes.
>
> You me
On 20/11/2009, at 18:20 , André Warnier wrote:
> Peter N Lewis wrote:
>> I already have:
>>MaxRequestsPerChild 1000
>> So the worker processes should die and clean that out.
>> I'm suspicious that the worker threads are not dieing because I've seen
>> cases where there are worker threads l
On 20 Nov 2009, at 09:59, Peter N Lewis wrote:
> On 20/11/2009, at 17:29 , André Warnier wrote:
>
>> Peter N Lewis wrote:
>>> I am having a serious problem with my site running out of memory. apache
>>> is leaking memory/processes.
You mentioned slicehost. I have a slice, and I see a problem
Peter N Lewis wrote:
I already have:
MaxRequestsPerChild 1000
So the worker processes should die and clean that out.
I'm suspicious that the worker threads are not dieing because I've seen cases
where there are worker threads listed in ps but not listed in server-status
(that will pro
On 20/11/2009, at 17:29 , André Warnier wrote:
> Peter N Lewis wrote:
>> I am having a serious problem with my site running out of memory. apache is
>> leaking memory/processes.
>
> Probably a lot more likely : your "mod_perl pages" are leaking memory.
> Perl will grab memory as needed, and onc
Peter N Lewis wrote:
I am having a serious problem with my site running out of memory. apache is
leaking memory/processes.
Probably a lot more likely : your "mod_perl pages" are leaking memory.
Perl will grab memory as needed, and once grabbed, will never release it
to the OS until perl itse
I am having a serious problem with my site running out of memory. apache is
leaking memory/processes.
I have half a dozen virtual hosts, but relatively light traffic, around 40,000
accesses per day (that includes all files on all hosts), so on the order of 1
access per second average.
Current
