Quote:
Originally Posted by jpollard
Then impose a proper MaxClients limit.
count them as 5 per processor (you could also divide your memory size by the data space used by apache, then subtract 10. If the result is below 10, use 10.)
The only reason to allow apache to multi-thread is support concurrent connections. If that overloads the system, the only reasonable thing to do is limit the number threads to what the hardware will support.
256 might be reasonable for my system (8GB with 8 cores), but personally, 10 is enough.
|
[Quote from link I posted]..."This isn't just the processes hanging for a little bit - or hanging for a few hours. They're hanging indefinitely. Not only does the Apache session hang - but the request from the client hangs as well. For example, if you go to google.com through a proxy, and it hangs, that request hangs forever as well. Now every time you try to connect back to the server it tries to send you to that Apache child. Which essentially makes the server unresponsive to you." -- pretty much describes EXACTLY what I'm experiencing, so my best guess is that it's a Glype-specific issue rather than an issue with Apache itself (I could be wrong though, feel free to speculate). I have made some modifications to apache2.conf and will monitor the situation in the meantime to see if it helps with the issues I've been experiencing (Specifically lowering MaxClients and other settings, however error logs showed MaxClients being hit around the time when I starting noticing the problems initially, so hopefully lowering the value isn't going to exacerbate the problem).
