cPanel - Apache Global Configuration

3,179 views

Published on

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,179
On SlideShare
0
From Embeds
0
Number of Embeds
530
Actions
Shares
0
Downloads
0
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

cPanel - Apache Global Configuration

  1. 1. Apache Global Configuration<br />Apache MPM (multi-processing modul) Common Directives<br />
  2. 2. Apache Architecture<br />
  3. 3. StartServers<br />- No of Child Server Process created when starting Apache. <br />- As the number of processes is dynamically controlled depending on the load, there is usually little reason to adjust this parameter.<br />
  4. 4. Minimum Spare Servers<br /><ul><li>Minimum no of Child Server Process will remain exist even Apache got nothing to do (idle)
  5. 5. Tuning of this parameter should only be necessary on very busy sites</li></li></ul><li>Maximum Spare Servers<br /><ul><li>Maximum no of Child Server Process will remain exist even Apache got nothing to do (idle)
  6. 6. Tuning of this parameter should only be necessary on very busy sites</li></li></ul><li>Max Clients<br /><ul><li>The MaxClientsdirective sets the limit on the number of simultaneous requests that will be served
  7. 7. Any connection attempts over the MaxClients limit will normally be queued
  8. 8. Once a child process is freed at the end of a different request, the connection will then be serviced.</li></li></ul><li>ServerLimit<br /><ul><li>This directive sets the maximum configured value for MaxClients for the lifetime of the Apache process.
  9. 9. If ServerLimit is set to a value much higher than necessary, extra, unused shared memory will be allocated
  10. 10. Highly recommend using the default setting unless you fully understand how it will interact with your Apache build and MaxClients setting.</li></li></ul><li>MaxRequestsPerChild<br /><ul><li>The MaxRequestsPerChild directive sets the limit on the number of requests that an individual child server process will handle.
  11. 11. After MaxRequestsPerChild requests, the child process will die.
  12. 12. If MaxRequestsPerChild is 0, then the process will never expire.</li></li></ul><li>Keep-Alive Timeout<br /><ul><li>The number of seconds Apache will wait for a subsequent request before closing the connection.
  13. 13. Once a request has been received, the timeout value specified by the Timeout directive applies.</li></li></ul><li>Max Keep-Alive Requests<br /><ul><li>The MaxKeepAliveRequests directive limits the number of requests allowed per connection when KeepAlive is on.
  14. 14. If it is set to 0, unlimited requests will be allowed.
  15. 15. Its recommend that this setting be kept to a high value for maximum server performance.</li></li></ul><li>Timeout<br /><ul><li>Amount of time the server will wait for certain events before failing a request
  16. 16. Example:
  17. 17. In mod_cgi, the length of time to wait for output from a CGI script
  18. 18. When reading data from the client, the length of time to wait for a TCP packet to arrive if the read buffer is empty</li>

×