平均负载试图衡量任何时间内的活动进程数量。
The load average tries to measure the number of active processes at any time.
例如，一个4CPU的系统可以承受的最大平均负载为5。
For example, a four-CPU system would have a maximum load average of 5.
平均负载的定义比较复杂，并且受到正在执行的进程的状态影响。
The definition of load average is complex and driven by the status of the processes that are executing.
看来CQLOAD是该计算队列的平均负载平均值。
It appears that CQLOAD, is the mean load average for that computing queue.
在多cpu(或多核)系统中，需要将平均负载除以cpu的个数。
In a multi-CPU (or multi-core) system, divide the load average by the number of CPUs.
高平均负载通常表示系统任务繁重，因而响应时间变慢。
High load averages usually mean that the system is being used heavily and the response time is correspondingly slow.
然而，要在web层支持平均负载，也有两个因素将影响硬件需求的评估。
However, there are two factors that will affect the estimation of the hardware requirement to support average load on the web tier.
通常在短时间内，计算机的平均负载可能比其最大平均负载高的多。
It is quite common to find a machine that has a load average that is significantly higher than its maximum for a short period.
然后它会提供三幅图表，以显示最近1分钟、5分钟和15分钟的平均负载。
It then provides three figures that show the load average in the last minute, five minutes, and fifteen minutes. For example.
要特别注意平均负载、磁盘空间消耗量和内存使用量；然后，总结出变化趋势。
Pay particular attention to load average, disk space consumption, and memory usage; then, formulate trends.
考虑到这一点，我们需要能够在一张图中显示系统平均负载和进程加载后产生的负载。
Consider being able to have access to a chart that displays both the average system load, as well as the load your process is generating on your system.
例如，当构建或编译一个应用程序、或执行一项磁盘密集型任务时，平均负载可能会激增。
For example, when building or compiling an application or performing a very disk intensive task, your load averages can shoot up.
在被当作CPU利用率的衡量标准时，虽然平均负载数是简单的和缺乏定义的，但远不是无用的。
As a measure of CPU utilization, the load average is simplistic, poorly defined, but far from useless.
在这个示例中，该计算机在最近1分钟、5分钟和15分钟内的平均负载分别超过了2、5和3。
In this example, the machine has had a load average of more than two in the last minute, more than five in the last five minutes, and more than three in the last fifteen minutes.
这样，我们不仅可以比较本文所描述的平均负载，而且可以比较前面提到的尖峰负载(15分钟快照)。
This will also allow us to compare not only the average loads described in this article, but the peak loads (15-minute snapshots) mentioned earlier.
在上面的情形中，好像有周期性的事件每20分钟发生一次，从平均负载图上显示的波峰可以看到这一点。
In the scenario above it seems that there is a periodic event happening every 20 minutes that cause a spike in the load average chart.
另一个需要被考虑的重要因素是，用户社区的地理分布，这也影响着系统的平均负载和最大负载。
Another important factor to consider is the geographic distribution of the user community which will also impact the average and peak load of the system.
在编写了这个小的可执行插件之后，接下来是使用Nagios注册该插件，并创建一个检查平均负载的服务定义。
With this small working executable in place, next is to register the plug-in with Nagios and create a service definition that checks the load average.
比方说，你想字在每次登录时打印一些关于你机器的很长的诊断信息，比如平均负载，内存使用情况，当前用户，等等。
Say, you'd like to print some lengthy diagnostic information about your machine each time you login (load average, memory usage, current users, etc).
负载的涨落是在无限处理能力的假设下计算的。算法在平均负载的计算上进行扩展，但避免了时间复杂度的增加。
The fluctuations are calculated with the assumption of unlimited resources, where the calculation is incorporated into the calculation of the average loads without adding to the time complexity.
使用在屏幕顶部附近的绿色菜单栏中提供的选项，我们能够选择查看更加详细的测试报告，比如，页面访问、CPU负载和平均负载时间。
Using the options provided in the green menu bar near the top of the screen, we could have chosen to see more detailed reports covering, for example, page access, CPU load, and average load times.
可以只在一天中的特定时间段提供服务(access_times选项)，或者只在机器的负载(以平均负载为准)低于阈值时提供服务。
You can provide the service during specific times of day (see the access_times option) or only if demand for the machine measured by the load average is below a threshold.
在每个用户负载点，我们平均生成并传递了70,000条消息。
We generated and delivered an average of 70,000 messages during each user load point.
要实现这种类型的负载，在各个页面请求之间，您需要平均 2.7秒的思考时间。
To drive this type of load, you would need an average of 2.7 seconds of think time between each page request.
只要满足了非功能性需求(负载能力、平均响应时间、峰值响应时间等)，应用程序就可以部署，用户也会觉得满意。
Once the non-functional requirements of a system (load capacity, average response time, peak-load response time, and so on) have been met the application can be deployed and the customer is satisfied.
该测试场景比较各种负载情况下的平均用户响应时间、探针响应时间、系统cpu利用率、占用的内存和磁盘利用率。
This test scenario compared average user response times, probe response time, system CPU utilization, memory used, and disk utilization at various loads.
我们将在图16系列中查看在更繁重的2,000个客户端的负载水平(平均利用率为45 - 60%)上这两个调优过的调控器的效果。
We'll look at the effects of the tuned governor on a heavier load of 2,000 clients (45-60 percent utilization on average) in the Figure 16 series.
图11：显示平均系统负载的eurekaj图表。
我们会继续增加负载生成器的个数，直到看到平均响应时间超过1秒为止。
We added additional load generators over time until we saw response times exceed one second on average.
查看图表中显示的平均探针时间，我们注意到，Groupware工作负载的平均探针响应时间在所有工作负载中是最高的。
When we reviewed the average probe responses represented on each chart, we noticed that the Groupware workload had the highest average probe response.
应用推荐