Pavel Sanda <[EMAIL PROTECTED]> writes:

>> > btw i dont think that just restart is the way how to solve it.
>> > there must be some httpd config which bound the number of httpd childern.
>> 
>> Is it the number of children that causes problems? There is also a
>> spamd process that has grown to +100M virtual memory.
>
> look again on the picture, i made more zoomed view.
> i would say there is stronger correlation with the green line - especially
> look on the start of the peaks.

If the httpd begin to use 1.6G of virtual memory, I am not surprised
that the load increases... The question is to know how this happened:
many medium-sized httpd processes, or on huge one?

JMarc

Reply via email to