This provides an indirect way to use ARFM to manage deeper tier resources.
这是一种使用ARFM间接地管理更深层资源的方法。
ARFM compares available backend resources to the requests waiting on the queues.
ARFM对可用的后端资源和队列中等待的请求进行对比。
ARFM enqueues a requests based on the service policy associated with the request.
ARFM根据与请求相关联的服务策略从队列中取出请求。
Autonomic request flow manager (ARFM) provides flow control for incoming workload.
自动请求流管理器(ARFM)提供对传入工作负载的流控制。
Lowering this value will reduce the volume of traffic ARFM will allow to the backend.
降低这个值会降低ARFM允许发送给后端的请求流量。
In practice ARFM anticipates and tolerates a certain level of inconsistency between requests.
在实践中，ARF m会预料到并容忍请求之间存在一定程度的不一致。
ARFM will try to avoid overloading nodes with the dynamic clusters running those applications.
ARFM尝试使运行这些应用程序的动态集群的节点避免出现超载。
In other words, the ARFM statistics of the co-located application server are distorted by ODR workload.
换句话说，共存应用服务器的ARFM统计数据会被odr工作负载影响。
ARFM makes predictions and calculations based on the observations of the traffic in each service policy.
ARFM根据对每个服务策略中的请求流的观察进行预测和计算。
This is because the application server, which is the resource tier that ARFM manages, is not overloaded.
这是因为应用服务器(即arfm管理的资源层)并没有过载。
The ARFM may queue requests if it detects the backend server may not be able to handle additional requests.
如果检测到后端服务器可能不能处理其他请求，ARFM可能会对请求排队。
However, ARFM ensures that lower priority service policies are breached by a greater extent than higher priority ones.
然而，ARFM确保低优先级的服务策略的违背程度总是大于高优先级的服务策略的违背程度。
However, there are peak load scenarios where ARFM cannot meet the service policy goals and avoid overloading the nodes.
然而，在一些出现峰值负载的场景中，ARFM无法满足服务策略目标以及避免节点超载。
In effect, this will cause ARFM to queue more traffic because there is effectively less backend capacity available to it.
实际上，这会导致ARFM让更多请求排队，因为它实际可用的后端处理能力少了。
Unfortunately, no ARFM policy currently exists that guarantees that the highest priority requests will never suffer rejection.
不幸的是，目前没有一项ARFM策略可以确保最高优先级请求永远不会被拒绝。
Therefore, ARFM rejection policies should only be used if some rejection of high priority requests is acceptable to the business.
因此，ARFM拒绝策略只有在企业允许拒绝高优先级请求的情况下使用。
WebSphere Virtual Enterprise provides you with different rejection policies that determine the behaviour of ARFM under such conditions.
WebSphereVirtualEnterprise提供了各种拒绝策略，可以确定ARFM 在这种情况下的行为。
If sufficient capacity does not exist, then ARFM will make trade-off decisions about which service goals will be breached and how badly.
如果没有足够的处理能力，ARF m会做折中的决策，考虑违反哪些服务目标，争取获得比较好的效果。
However, this action can only be taken if ARFM was queuing traffic for the service policy, which was not the case in the previous example.
但是，这种措施只能用于ARFM正在让此服务策略的请求流排队的情况，而前面的示例不是这种情况。
ARFM continues to profile the gold traffic and increase the expected service time due to the higher actual service times it is now seeing.
ARFM分析gold请求流，由于它现在看到的实际服务时间增加了，它会提高预期服务时间。
Until a system is properly configured with appropriate service policy definitions, consider disabling the traffic queuing function of ARFM.
如果还没有为系统配置适当的服务策略定义，应该考虑禁用ARFM的请求排队功能。
This means that ARFM assumes that any two requests that fall into the same service policy have similar response times and CPU requirements.
这意味着，ARFM假设属于同一服务策略的任意两个请求具有相似的响应时间和CPU需求。
This means that ARFM requires some wiggle room between the typical service time of a particular class of traffic and the desired service goal.
这意味着，ARFM要求请求流的典型服务时间与预期服务目标之间存在一些余量。
When requests enter the on Demand Router, ARFM queues them and makes decisions about when to dispatch them to the backend application servers.
当请求进入OnDemand Router时，ARFM把它们放在队列中并决定什么时候把它们分派给后端应用服务器。
ARFM manages the first tier of capacity only and correcting this situation would require insight into the resource utilization at deeper tiers.
ARFM只管理第一层的处理能力，而纠正这种情况需要了解更深层上的资源利用率。
The first is to reduce the time ARFM keeps the request in the queue for traffic in that service policy (thus reducing the overall response time).
第一种是，对于某一服务策略的请求，减少请求在队列中停留的时间（从而减少总响应时间）。
By default, this is set to 90% meaning that ARFM will not queue any traffic until the application server CPU utilization would otherwise exceed 90%.
在默认情况下，这个值设置为90%，这意味着在应用服务器CPU利用率即将超过90%之前ARFM不会让任何请求流排队。
The ODR runs the application request flow manager (ARFM), which USES CPU resources that can no longer be used by the co-located application servers.
ODR运行应用程序请求流管理器(ARFM)，后者使用的CPU资源永远不会被用于共存的应用服务器。
Service Goal – the response time target which ARFM will attempt to meet for the set of Transaction Classes associated with a particular Service Policy.
服务目标（Service Goal） –对于与特定服务策略相关联的事务类，ARFM尝试满足的响应时间目标。
Note that the current CPU utilization value is estimated by ARFM based on the predicted characteristics of the requests it has permitted through the system.
注意，ARFM根据允许穿过系统的请求的预期特征来估计当前的cpu利用率。
应用推荐