{"id":28,"date":"2015-01-13T06:29:00","date_gmt":"2015-01-13T06:29:00","guid":{"rendered":"http:\/\/www.asianux.org.vn\/index.php\/2015\/01\/13\/apache-optimization\/"},"modified":"2015-01-13T06:29:00","modified_gmt":"2015-01-13T06:29:00","slug":"apache-optimization","status":"publish","type":"post","link":"https:\/\/www.asianux.org.vn\/index.php\/2015\/01\/13\/apache-optimization\/","title":{"rendered":"Apache Optimization"},"content":{"rendered":"

The default Apache settings that cPanel sets upon install are definitely something that can be improved on. With a few small tweaks, the efficiency with which Apache runs with can be greatly improved.
Please noted: This article assumes that you are using a Linux server running Apache and cPanel or Plesk, and that you are familiar with editing files from the command line.<\/a><\/small>
<\/span>
To start, open the Apache configuration file and finding the directives section. On a cPanel server, it will be located in \/usr\/local\/apache\/conf\/. On a Plesk server, it will be in \/etc\/httpd\/conf\/. If you are using vi or vim: once you open the file, you can find the directives by scrolling through the file, or by typing forward-slash \u2018\/\u2019 and typing the exact string that you are looking for (search is case specific).
[root@host \/] vim \/usr\/local\/apache\/conf\/httpd.conf<\/code>
or
[root@host \/] vim \/etc\/httpd\/conf\/httpd.conf<\/code>
This list is a composite of the settings we will be reviewing from fresh install on a cPanel server: <\/p>\n

Timeout 300
KeepAlive On
MaxKeepAliveRequests 100
KeepAliveTimeout 15
MinSpareServers 5
MaxSpareServers 10
StartServers 5
MaxClients 150
MaxRequestsPerChild 0<\/code><\/p><\/blockquote>\n

Please note, the settings that we will review in this article are by no means a complete list of tweakable options in the Apache configuration file. The settings we will be focusing on are the ones that control how Apache handles webpage requests.<\/em>
Timeout<\/strong> <\/p>\n

Timeout 300<\/p><\/blockquote>\n

Usually this value doesn\u2019t require editing and a default of 300<\/strong> is sufficient. Lowering the \u2018Timeout\u2019 value will cause a long running script to terminate earlier than expected.
On virtualized servers like VPS servers, lowering this value to 100<\/strong> can help improve performance.
<\/strong>
KeepAlive<\/strong> <\/p>\n

KeepAlive On<\/p><\/blockquote>\n

This setting should be \u201cOn\u201d unless the server is getting requests from hundreds of IPs at once.
High volume and\/or load balanced servers should have this setting disabled (Off<\/strong>) to increase connection throughput.
<\/strong>
MaxKeepAliveRequests<\/strong> <\/p>\n

MaxKeepAliveRequests 100<\/p><\/blockquote>\n

This setting limits the number of requests allowed per persistent connection when KeepAlive is on. If it is set to 0, unlimited requests will be allowed.
It is recommended to keep this value at 100<\/strong> for virtualized accounts like VPS accounts. On dedicated servers it is recommended that this value be modified to 150<\/strong>.
<\/strong>
KeepAliveTimeout<\/strong> <\/p>\n

KeepAliveTimeout 15<\/p><\/blockquote>\n

The number of seconds Apache will wait for another request before closing the connection. Setting this to a high value may cause performance problems in heavily loaded servers. The higher the timeout, the more server processes will be kept occupied waiting on connections with idle clients.
It is recommended that this value be lowered to 5<\/strong> on all servers.
<\/strong>
MinSpareServers<\/strong> <\/p>\n

MinSpareServers 5<\/p><\/blockquote>\n

This directive sets the desired minimum number of idle child server processes. An idle process is one which is not handling a request. If there are fewer spareservers idle then specified by this value, then the parent process creates new children at a maximum rate of 1 per second. Setting this parameter to a large number is almost always a bad idea.
Liquidweb recommends adjusting the value for this setting to the following:
Virtualized server, ie VPS 5<\/strong>
Dedicated server with 1-2GB RAM 10<\/strong>
Dedicated server with 2-4GB RAM 20<\/strong>
Dedicated server with 4+ GB RAM 25<\/strong>
MaxSpareServers<\/strong> <\/p>\n

MaxSpareServers 10<\/p><\/blockquote>\n

The MaxSpareServers directive sets the desired maximum number of idle child server processes. An idle process is one which is not handling a request. If there are more than MaxSpareServers idle, then the parent process will kill off the excess processes.
The MaxSpareServers value should be set as double the value that is set in MinSpareServers.
<\/strong>
StartServers<\/strong> <\/p>\n

StartServers 5<\/p><\/blockquote>\n

This directivesets the number of child server processes created on startup. This value should mirror what is set in MinSpareServers.
<\/strong>
MaxClients<\/strong> <\/p>\n

MaxClients 150<\/p><\/blockquote>\n

This directive sets the limit on the number of simultaneous requests that will be served. Any connection attempts over the specified limit will be queued. Once a process is freed at the end of a different request, the queued connection will then be served.
For virtualized servers such as VPS accounts, it is recommended to keep this value at 150<\/strong>. For all dedicated servers the recommended value for this setting is 250<\/strong>.
MaxRequestsPerChild<\/strong> <\/p>\n

MaxRequestsPerChild 0<\/p><\/blockquote>\n

This directive sets the limit on the number of requests that an individual child server process will handle. After the number of requests reaches the value specified, the child process will die. When this value is set at 0, then the process will never expire.
Liquidweb recommends adjusting the value for this setting to the following:
Virtualized server, ie VPS 300<\/strong>
Dedicated server with 1-4GB RAM 500<\/strong>
Dedicated server with 4+GB RAM 1000<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

The default Apache settings that cPanel sets upon install are definitely something that can be improved on. With a few small tweaks, the efficiency with which Apache runs with can be greatly improved. Please noted:…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"class_list":["post-28","post","type-post","status-publish","format-standard","hentry","category-optimization"],"_links":{"self":[{"href":"https:\/\/www.asianux.org.vn\/index.php\/wp-json\/wp\/v2\/posts\/28","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.asianux.org.vn\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.asianux.org.vn\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.asianux.org.vn\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.asianux.org.vn\/index.php\/wp-json\/wp\/v2\/comments?post=28"}],"version-history":[{"count":0,"href":"https:\/\/www.asianux.org.vn\/index.php\/wp-json\/wp\/v2\/posts\/28\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.asianux.org.vn\/index.php\/wp-json\/wp\/v2\/media?parent=28"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.asianux.org.vn\/index.php\/wp-json\/wp\/v2\/categories?post=28"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.asianux.org.vn\/index.php\/wp-json\/wp\/v2\/tags?post=28"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}