I have recognized, the program java and syncserver consume most of the resource, but i think this could not be the only reason for the slow down problem. Recently, the web site has been performing well, the problem just happened today. Could you pls help us to figure it out?
This is because you have hit the MaxClients directive in apache, which specifies how many simultaneous connections to apache can be open:
(~) # pstree | grep httpd
|-httpd---256*[httpd]
(~) # grep MaxC /etc/httpd/conf/httpd.conf
# ServerLimit: maximum value for MaxClients for the lifetime of the server
# MaxClients: maximum number of server processes allowed to start
MaxClients 256
As a result, any connections over that 256 end up being queued up to wait for a process to open. In a situation where you already have an overworked java server, this can lead to a snowball effect as it consumes more and more system resources, making apache slower and slower to respond.
Largest Current httpd Memory Usage: 17.76MB
Apache MaxClients Setting: 256
Total System Memory: 3956.82MB
Maximum Apache Memory Usage: 4549.00MB (114.96%)
Maximum Recommended MaxClients Setting: 211
Unfortunately, we can't safely up the MaxClients much higher than they already are due to the fact that they are already set in such a way that they can consume more memory than the server actually has.
We can restart apache to free those connections for the short term, but I suspect that this issue will clear itself up if the java/syncserver issue is resolved.
Post new topic
)
)
Quote
Edit 
