I don’t know what kind of traffic you are seeing that would require such settings, but it seems like your settings could be lowered to make better use of resources since it seems like you are overcommitting Apache from the get-go & do not have it configured for realistic site traffic. Unless you can provide some site stats that justify the high numbers of the initial config.
MaxRequestsPerChild which will help prevent memory leaks by re-spawning parent processes more often. Also, I lowered
MaxClients since that is related to how many clients are connected PER SECOND. So if someone grabs a page from your site, and it renders in 1 second, guess what? The server has done it’s job. Related to that I lowered
MaxKeepAliveRequests and the
KeepAliveTimeout to be more realistic again. I also lowered the general
Timeout since 120 seconds is 2 minutes. If a client is taking 2 minutes to get content from you that is more than a generous amount of time to give them before the server times out. I like to keep that number in place just in case a high traffic scenario comes around.
Remember: A web server doesn’t keep a constant connection between the server and the client. A client makes a request, the server delivers the page and that’s it. So tune with that in mind. Also, please read this other answer I provided to another poster who was worried about memory usage on their web server.