Tuning apache
Test tool
http://www.acme.com/software/http_load/Parameters
| Parameter | Explaination |
| MaxClients | Determines how large is each httpd process, then multiple by MaxClients. Should not exceed physical mem |
| MaxRequestsPerChild | number of requests handled by each child, before the process is terminated. This prevent memory leak. Set this to 3000 or 5000. |
| KeepAlive | [On|Off] Tells apache whether to close a connection immediately a request has been filled. If a page contains seberal js, several images, and several of others, turning on KeepAlive will save the time and resource to estabish tcp connections for each and one of those objects. But because connections are maintained for some period of time, apache's resource is not fully used for serving maximum number of clients. In long run, turning on KeepAlive means more MaxClients is required. |
| KeepAliveTimeout | [15] Try set it to short period of time, thus benefit from KeepAlive while not overload server with inactive connections. |
| MaxKeepAliveRequests | [100] - How many requests a client can make within one connection |
| worker MPM | many child processes, each has many threads |
| BufferedLogs On | Writes log to memory and write to disk in batch |
| ForensicLog filename | Writes logs for forensic use |
* prefork MPM: many child processes, each has 1 thread. Consumes more memory
High cpu usage
This is unconfirmed. If your apache parent process is taking up a lot of CPU load and you know it's not because of cgi / php, perhaps apache is too busy forking and unforking. In that case, raise the following parameters:StartServers 10 MinSpareServers 10 MaxSpareServers 50
There are no comments on this page. [Add comment]