I am using WHM, and need some help about what I see under “Apache Status” [closed] – Problems with loading a website are often blamed on the Internet connection, but even the most perfectly set up network cannot help if there is no service to reply at your destination. One of the most popular HTTP servers used for this task is Apache2. Much of Apache’s popularity can be attributed to its easy installation and use, but never the less it is possible to run into problems with even the easiest of the software. If you’ve encountered an issue loading your web page, follow these simple troubleshooting methods outlined in this guide to attempt to get your web server back up and working again. Below are some tips in manage your apache2 server when you find problem about apache-2.2, , , , .
I’ve been noticing that my server has been using a lot of CPU for Apache processes when it really shouldn’t be. Screenshot of Apache Status:
It seems like the Apache CPU% should be more like .0045%? My traffic is under 4 million pageviews per month.
From what I’ve read, each period “.” is a process to receive a request. I think I have way too much dedicated to Apache, so I’d like to cut them back. Unfortunately I don’t know much about apache and could use some guidance.
So how do I lower the amount of slots open for connections?
The periods are unused slot that don’t have processes behind them. The other scoreboard entries have or had processes behind them as per the legend after the scroreboard. On recent Apache releases the scoreboard reports all slots. ServerLimit (default 256) sets the size of the scoreboard. Setting this smaller may save some memory and disk space.
MaxClients limits the number of processes you can have. Setting it too low can cause clients to get failed connection requests. MaxClients must not be more than ServerLimit.
It looks like you have 10 processes, 2 serving requests, and 8 idle servers. StartServers, MinSpareServers, and MaxSpareServers control the number of servers at any one time. Threading servers use SpareThreads in place of SpareServers. These can be tuned to limit the number of processes, but setting the values too low will result in heavy load spawning new servers. It appears apache is using 34% of a CPU. 124 seconds user time and 11 second system time during 6.3 minutes.