> >> > 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?
so, watching last few hours the system processes during the slowness phase its clear that the number of httpd childs keeps longly around the number of 50 with ~1.6 GB of virtual memory and the system have problems to get back into the sane state. I suggest that we find by some bisecting the number of maximum childern, which is aussie able to survive. JMarc, could you try to change the line in httpd.conf MaxClients 48 into eg 24 and restart httpd? we can give it some trac-test to see how will aussie manage it. pavel
