将英语翻译成中文（机器翻译的不要）...

将英语翻译成中文（机器翻译的不要）...
Optimizing Apache Server Performance
Squeezing the most performance out of your Apache server can make difference in how your Web site functions and the impression it makes. Even fractions of a second matter, especially on dynamic sites. This article looks primarily at configuration and installation, two areas where you have the most control.
Measuring and Improving Performance
Apache was designed to be as fast as possible. It's easy, with a fairly low-powered machine, to completely saturate a low-end Internet link with little effort. However, as sites become more complex and the bandwidth needs of different connection types increase, getting the best performance out of an Apache installation and Web sites becomes more important.
Enhancing performance means nothing if the changes achieved are only minor gains. Spending hours or even days finely tuning a server for just a few percentage points is a waste of time. The first step, therefore, is to determine how fast the server is running and its general performance level so you can work out how to improve performance and measure the changes.
This is not the first time we've discussed Apache testing (see Staying Out of Deep Water: Performance Testing Using HTTPD-Test's Flood). As was noted previously, determining which parts of your Web application are causing the problem — particularly identifying whether it's Apache or the application environment you are using with dynamic sites — can be difficult. Identifying problems in dynamic applications is beyond the scope of this article, but we will look at ways to generally improve the speed of Apache and how it interacts with other components to support a Web site.
Host Environment
Regardless of operating system, the following optimization principles apply:
• Keep other background applications to a minimum. If you are really serious about performance, this should even include some background processes that some would consider vital. For example, in Unix, switch off NFS, any printing services, and even sendmail if it's not needed. Under Windows, use the System control panel to optimize the system for applications and system cache, and optimize the system for performance. Make sure, of course, any required applications or services, like MySQL are still running.
• Avoid using the system.If you start compiling applications, editing files, or otherwise employing the machine, you'll reduce its Web serving performance. If you must edit components or install software, build or edit the components on another machine and copy them over.
• Keep your system up to date. Although a good idea just from a security point of view, software patches and updates can make significant improvements to network and I/O performance.
强调：不敢劳你机器大架，俺要的是人工翻译，翻译好的，追加分数

不好意思,对计算机服务器不是很懂.看下面的
优化Apache 服务器的性能
过分透支你的Apache服务器的性能并不会明显改善你的网站的运行和它给浏览者的印象.对于后者,尤其指动态网站.这篇文章主要讲配置和安装,在这两个方面您控制最多.
衡量和改善性能
Apache特点是越快越好.这很容易办到,只要通过十分低功率的机器,不要怎么费事就可以完全渗透低端的网络连接.尽管如此,由于网站越来越复杂,对于不同连接类型的带宽需求增加,通过Apache的安装和网站变得更加重要.
取得细微的变化对于提高性能来说没有任何意义.巧夺天工似的花费数小时或很多天将服务器的性能提高几个百分点无疑是在浪费时间.因此,第一步就是决定服务器的速度有多快和大致性能级别,如此你就能知道怎么样改进性能和衡量变化了.
我们不是第一次讨论Apache的评测.我们以前说过的,决定你的网络的那些部分引起了这个问题,尤其是分开是Apache的问题或是你的动态网页的应用环境的问题,这会很难.动态应用的问题辨别不是这篇文章的范围,但是我们会寻求方法以达到大致改进Apache的速度和Apache如何与其它部分配合支持一个站点的运行.
主机环境
无论是什么系统,遵循下面的优化原则：
减少其它的后台应用.如果你十分在意服务器的性能的话,后台应用甚至可以包括一些常规意义认为是十分关键的后台进程.举例说,在Unix系统下,关掉NFS,以及任何打印相关的服务,甚至是发送邮件,如果不需要的话.在Windows系统下,用系统控制台在应用程序和系统缓存设置中优化系统,设置性能选项卡来优化系统.当然保证必要的应用程序或者服务,（如Mysql）仍在 运行.
避免使用这个系统.如果你开始编译应用程序,编辑文档,而使用这台机器,这就会降低它的网络服务器的性能.如果必须要编辑程序或是安装软件的话,在另一台机器上操作,之后再复制过来.
保持你的运行系统不断更新.虽然从安全的角度考虑,不时常更新系统很好,但是软件补丁和更新会显著改进网络和输入输出设备的性能.