Apache performance tips

Apache is correct in the first place, the speed in the second of the common Web server.

Even so, its performance is very satisfactory. Many sites only to 10M exports bandwidth. Apache to the site of the low-end Pentium servers at work. In fact, to have more bandwidth for the site for some reason (such as a large number of CGI and database transaction processing) need to use one or more machines to meet the bandwidth requirements. These are the reasons for the previous Apache development work focused on the correctness and configurability. Unfortunately many people emphasize certain indicators and their assessment of the original data as a Web server or bad standards. Commonly accepted standards is the "original minimum performance (bareminimumperformance)", in which other than speed index applies only to a small segment of the market demand. But in order to avoid Apache in some markets in the marginalized, on a fairly Apache1.3, associate it with the gap between high-end servers. Others just want to try these things can run much faster. These people try to put the Apache last drop of performance out of the way, they also want to see what impact the performance of Apache. The rest of the article is written for them. Note This article applies to the Apache1.3 on UNIX, the section applies to the NT platform. The current Apache on NT has not been in optimization. In fact, different programming model makes it in the performance of the NT is not good. (The POSIX model. NT with the POSIX subsystem simulation such programming standards, efficiency is very low. Apache2.0 abandoned the POSIX dealing directly with the operating system, performance will leap – translator's note) on hardware platforms and operating systems most directly affect Web server performance hardware RAM you want to number. A Web server never should access memory Exchange area. Exchange has added the delay time for each request, the user is therefore of the view that the "fast enough." They will click on [stop] and reload the page, which will further increase the burden on the server. You can also adjust the MaxClients is necessary so that your server does not give rise to too many child processes which lead to Exchange. In addition to this thing not so critical. Have a fast CPU and fast card and hard disk can make your server "fast enough." In fact, these words are fast enough experience to experience required. The operating system of choice is a major issue, as appropriate. Common criteria is: get the OS vendor's latest TCP/IP patch. The rapid emergence of HTTP service broke up to 1994 and 1995, the UNIX kernel settings in many scenarios. Ideal choices include current FreeBSD and Linux. On the run-time settings (Run-TimeConfiguration) HostnameLookups 1.3 previous Apache, the default value of the HostnameLookups is On, this will cause each request to the server for NDS query, thus increasing the latency. Set the default Apache1.3 to off. In 1.3 and later versions, if you use any allowfromdomain or denyfromdomain command, the cost will be the two DNS query of delay (in a reverse query followed by a forward queries to ensure that the results of the former is true). Therefore in order to get the best performance you should avoid using HostnameLookups (using IP address instead of a domain name is also a good idea). Limit the use of commands is possible, such as using a similar container. In this case, the DNS query occurs only in compliance with the conditions of the request. The following example enables the query occurs only in .html and .cgi files request: HostnameLookupsof