有些计算机可能变得过载，所以如果增加更多的计算机，并在解决方案中增加负载均衡能力，让每台机器承担一部分负载，就会在整体上形成更好的响应时间。
Some computers can become overloaded, so if you add more computers and combine load balancing into the solution, each computer takes a fraction of the load, leading to better response times overall.
第2部分中关于将RationalPerformance Tester用于负载测试的基本知识也非常重要，它使您能够处理本文中更加复杂的活动。
It's also important that you have learned the basics of using Rational Performance Tester for load testing from that article, so that you can proceed to the more complex activities in this one.
第3部分(本部分)介绍了不同用户负载的测试(请参见下一小节)。
Part 3 (this part) covers testing as user loads grow (see the next section for more).
这一分散式策略被应用于负载信息交换，并且应用于进程迁移期间。
This decentralized strategy is applied in the load information exchange and at the process-migration stage.
本系列文章的第3部分阐述了如何使用中介阅读和更改消息有效负载。
Part 3 of this series of articles explained how to read and change message payloads using a mediation.
在这种情况下，图2中的完整工作负载管理分两个级别提供。
In this context, the complete workload management in Figure 2 is provided at two levels.
如果它很少运行或没有导致生产问题并且是工作负载的一部分，我们将在下周维护期间对它进行调优。
If it runs infrequently or is not causing production issues and is part of the workload, we'll tune it for next week during our weekly maintenance.
测试团队可以使用按照准确的测试用例百分比组合开发的测试用例对环境进行负载和压力测试。
The test team can load and stress the environment using the test cases they developed at the correct percentage mix of test cases.
如果此每15分钟活动用户的成本保持平坦，但总的cpu时间线上升(或下降)，我们就可以断定，这是一个与工作负载或容量相关的问题。
If this cost per active 15-minute user stays flat, but the total CPU line goes up (or down), we can conclude that this is a workload or a capacity related issue.
一般来说，对于个别测试，您应该只在最大负载级别上运行下面描述的个别测试和配置点，运行时间最多为10至30分钟。
Typically, the individual tests and configuration points that are described below should only be run at the peak load level for an individual test for a maximum of 10 to 30 minutes.
它还为第3部分打下了基础，在第3部分中，您将运行不同用户负载规模的测试。
It is also essential preparation for Part 3, where you will run tests on increasing sizes of user loads.
这样，我们不仅可以比较本文所描述的平均负载，而且可以比较前面提到的尖峰负载(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.
一次只关注一个应用程序——它的工作负载和它所访问的一部分模式。
Focus on a single application at a time — its workload and the parts of the schema that it accesses.
对于系统十分成熟的构建来说，团队将根据系统特定的方面进行负载测试或者功能测试。
For builds where the system was sufficiently mature, the team would perform load tests or function tests against specific aspects of the system.
在上面的情形中，好像有周期性的事件每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.
对于产品应用程序，研究预期的工作负载并开发一个最接近现实的测试装具模块十分关键。
For production applications, it is critical to study the expected workload and develop a test harness that mirrors reality as much as possible.
特定目的的负载测试只是我们测试工作中的一小部分，但是它在整个系统的测试中却是非常重要的。
Load testing in particular had played only a small part in our testing efforts so far but would figure prominently in our testing of the full system.
我们看到，每个活动了15分钟的用户的处理器成本从.07减少至. 05秒，这意味着运行相同工作负载所需的处理器资源减少大约28%。
We saw the processor cost per active 15-minute user go from.07 to.05 processor seconds, which means a reduction of about 28 percent to run the same workloads.
在处理拥有大量空白或重复数据的大型文件时，ZIP是一种十分优秀方法，能够降低带宽负载或存储设备使用量。
ZIP is a great way to reduce bandwidth overhead or storage usage when handling large files that have a lot of white space or repeated data.
最好是在一定的时间范围内来考虑负载问题；例如，在特定的时间范围内访问该站点的用户数量，也许是以五分钟作为时间间隔，也许是每小时。
It is better to think about load over time; for example, a number of users accessing the site within a specific time frame, perhaps over five minutes or per hour.
最后，负载信息显示了应该报告的1、5和15分钟中的CPU的最大负载。
Finally, the load information shows the maximum CPU load for 1, 5, and 15 minutes that should be reported.
这种方案是出于以下考虑而布置的：在TPC-H工作负载中，相当大一部分I/O操作都是连续的读取操作。
This arrangement is made with the following concern: in the TPC-H workload, a significant amount of I/O operations are sequential reads.
如果工作负载接近或大于40%，您就需要升级现在的网络，或创建一个新的网内集群网络(如本系列第1部分所述)。
If the workload is already at or near 40% or more, you will need to upgrade the existing network or create a new intra-cluster network (as described in part 1 of this series).
单用户数据库应用程序非常少见，因此考察并发工作负载的性能行为十分重要。
Single-user database applications are very rare, so it is important to look at the performance behavior of a concurrent workload.
每个事务被分配一个权重，这个权重决定这个事务在工作负载中的百分比。
Each transaction is assigned a weight that determines the transaction's percentage in the workload mix.
本系列文章的第2部分和第3部分将讨论在不影响您先前所录制的测试脚本的情况下，有效地降低用户负载所需要考虑的事项。
Parts 2 and 3 of this series will discuss considerations for effectively breaking down user loads easily without affecting the test scripts previously recorded.
如果必须为工作负载分区设置最小资源量或最大资源量，就需要使用基于百分比的控制方法。
If a minimum resource amount or a limit of the maximum amount of a resource must be set for a workload partition, then percentage-based controls need to be used.
我们来看程序的第一部分，其中定义了用于处理传入的xml有效负载的方法。
Look at the first part of the equation, where you define the methods that are used to handle the incoming XML payload.
关于第三部分如何测试不同规模的用户负载？
如果它很少运行或没有导致生产问题并且是工作负载的一部分，我们将在下周维护期间对它进行调优。
F it runs infrequently or is not causing production issues and is part of the workload, we'll tune it for next week during our weekly maintenance.
应用推荐