客户机模式性能可能因网络负载，甚至断开连接的点的不同而不同。
Client mode performance can vary with network load, even to the point of breaking the connection.
这一点可以解释为什么人们常常在“夜晚”(此时的后端资源处在轻(或更轻的)负载条件下)运行性能测试。
This explains why performance tests are often run "overnight" when backend resources are subject to light (or lighter) load conditions.
一般来说，对于个别测试，您应该只在最大负载级别上运行下面描述的个别测试和配置点，运行时间最多为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.
但是应该注意一点，由于这不是正式的JAX - RS框架基准测试，改变负载和测试条件可能会导致不同的结果。
However, it is important to note that because this is not a formal benchmark for JAX-RS frameworks, varying loads and testing conditions might cause different results.
如果测试没有使服务器负载达到临界点，则有些问题将检测不到，所以要确保服务器的负载超过您预期的最高峰流量。
If the tests don't load the server to the point where things break, you won't detect some of the problems, so be sure you load your server beyond your expected peak traffic.
为了说明这一点(即SOAP有效负载数据的随意性)以及在客户机与服务间就数据编码达成一致的需要，我们采用了下面的示例。
To illustrate this point about the arbitrary nature of SOAP payload data and the necessity for an agreement upon data encoding between the client and the service take the following example.
这种情况下更重要的一点是，站点在如此高的负载下不会发生崩溃。
And it's all the more important at such times that they be able to degrade gracefully under such high load.
在产生该信息的实际测试中，我的确可以将比率再增大一点，但是我认为可能会在负载生成服务器中碰到CPU的限制。
In the actual test on which this information is based, I may have actually been able to go a little higher, but I think I was getting CPU bound on the load generation servers.
在现在为止，我们没有看到性能的问题，因为在测试的任何一个点上CPU的负载从没变得紧张。
For now, we didn't see this as a performance concern, since the CPU load never become stressed at any point in the test.
负载曲线中有一点表示响应时间的增加的直接原因是应用程序处理的请求的数量。
There is a point in the load curve where response time degradation is directly due to the number of requests the application is processing.
在上面的情形中，好像有周期性的事件每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.
这个有效负载表示在扫描器发现系统的入侵点之后将在系统上运行的代码。
This payload represents the code that will be run on a system after the scanner discovers an entry point into the system.
需要记住的一点是，只有不密切请求能被负载平衡。
The point to remember is, that only non-affine requests can be load-balanced.
考虑到这一点，我们需要能够在一张图中显示系统平均负载和进程加载后产生的负载。
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.
当数据库在支持多个安排为负载平衡配置的前端服务器时，这一点特别关键。
This is especially critical when a database is supporting several front-end servers that are arranged in a load-balancing configuration.
可以使用新的配置参数rto_server_restart实现这一点，该参数允许监视工作负载，并及时触发检查点以满足rto策略，从而进行故障恢复。
You can do this using a new configuration parameter, RTO_SERVER_RESTART which enables failure recovery by monitoring the workload and triggering checkpoints in a timely manner to meet the RTO policy.
正如繁忙交叉点处的流量需要备份一样，系统关键区域的数据也只会在负载量大时才会备份。
Just as traffic backs up at some intersections only in heavy traffic, data can back up in your system in critical areas only when under heavy load.
如果程序出现不正常的高内存负载、频繁无响应或内存溢出，通常最好的分析切入点是查看内存对象。
If your application is experiencing unusually high memory load, frequent freezes or OOME, its often most useful to start by understanding just what kind of objects are present in memory.
这一点可以实现把浪费降到最低，不会给员工和设备带来过度的负载，也不会出现不均衡的生产水平。
This helps achieve the goal of minimizing waste (muda), not overburdening people or the equipment (muri), and not creating uneven production levels (mura).
新增的“currentlycommitted”锁语法可以消除读和写工作负载之间的冲突，让数据库实现真正的时间点响应。
A newly added "currently committed" locking syntax eliminates the conflict between read and write workloads so the database can deliver a true point-in-time response.
为了达到忽略提供给Design Advisor的工作负载中的SQL的程度，在解释建议时应该记住这一点。
To the extent that you omit SQL from the workload you provide to the Design Advisor, you should bear this in mind when interpreting the recommendations.
从单一控制点监视和分析多个运行各种工作负载的DB 2实例—oltp、数据仓库和企业内容管理。
Monitor and analyze multiple DB2 instances running a wide variety of workloads - OLTP, data warehouse, and enterprise content management - all from a single control point.
现在您已经构建了可以处理和返回xml有效负载的自定义web服务，接下来在清单9中看一下如何实现这一点的一个简单代码示例。
Now that you've built the custom web service that can handle and return XML payloads, look at a simple code example of how to do this in Listing 9.
稍微高级一点的主题：聊天服务器的负载平衡。
然后看了通过创建自定义切入点对SugarCRMweb服务使用xml有效负载的代码。
You then looked at the code to add the ability to use XML payloads with SugarCRM web services by creating a custom entry point.
点触屏幕上的任意位置，然后选择负载设计。
结果表明，九点控制器在电机参数变化以及负载突变时都有较好的控制性能。
Simulation experimental results proved that the nine-point control has good performance under the above-mentioned circumstances.
系统同时采用TMPPT方式使太阳电池尽可能工作在最大功率点处，为负载提供最大的能量。
The system uses the TMPPT mode to make the solar battery work at the most power point, and provides the most energy for the load at the same time.
系统同时采用TMPPT方式使太阳电池尽可能工作在最大功率点处，为负载提供最大的能量。
The system uses the TMPPT mode to make the solar battery work at the most power point, and provides the most energy for the load at the same time.
应用推荐