Effect of processing rates on queue depth.
处理速率对队列深度的影响。
Queue depth events could be used to initiate configuration changes.
队列深度事件能够用于发起配置更改。
And queue depth in the agent command queue changes from zero to one.
且代理命令队列中的队列深度从0变为1。
The queue points current queue depth is displayed, as Figure 7 shows.
队列点当前队列深度将显示出来，如图 7 所示。 查看图 7 的大图。
The minimum queue depth shows how shallow the measurement object pool got.
最小队列深度显示了度量对象池有多浅。
The queue depth exceeds the threshold set by TRIGDEPTH; a trigger fires.
队列深度超过TRIGDEPTH设置的阈值时，触发器触发。
When the queue depth is displayed, it does indeed contain exactly 800 messages.
但队列深度显示时，它的确正好包含800条消息。
To keep the queue depth low, the server process would have to run at a higher rate.
为了保持队列深度值较低，服务器进程必须以更高的速率运行。
As noted earlier, the queue manager disables triggering when a trigger is fired, based on queue depth.
如前所述，当触发器触发后，队列管理器基于队列深度禁用触发机制。
This sequence of events repeats each time the queue depth builds beyond the threshold configured in TRIGDEPTH.
每当队列深度超过 TRIGDEPTH中配置的阈值时，这个事件序列都会重复。
When you evaluate queue depth requirements, message processing rates are just as important as peak message volumes.
当评估队列深度要求时，消息处理速率和峰值消息量同样重要。
If the queue depth is high, assume that the application is not healthy or able to cope with the rate of messages.
如果队列深度比较高，则假定应用程序不健康或不能够处理消息的速率。
Here, you are inquiring on the current and maximum queue depth, the maximum message length, and the value of QDEPTHHI.
这里，您查询的是当前和最大队列深度、最大消息长度、以及QDEPTHHI的值。
You should not do anything with them, but it might be interesting for you to see the queue depth of some of the queues.
不应对其进行任何操作，但可以通过这样了解一些队列的队列深度。
And if the queue depth had been set to the 5000 calculated earlier, it would have been exceeded within the first half an hour.
如果队列深度设置为前面所计算的5000，在半个小时内就会超个这个值。
In the example below, the message putting rate is twice as fast as the getting rate, and you can see the queue depth growing rapidly.
在下面的示例中，消息的传入速率为提取速率的两倍，而您会发现度量深度迅速地增加。
The audit maximum incoming queue depth shows how many measurement objects were waiting on the queue to be processed by the audit thread at any one time.
审计最大传入队列深度显示了同一时刻有多少个measurement对象正在排队等候审计线程处理。
Make sure that the maximum defined queue depth for this queue is sufficient to store messages, and monitor it to ensure that the maximum depth is not exceeded.
请确保为这个队列定义的最大队列深度对于存储消息来说足够大，并且对它进行监视以确保不会超过最大深度。
There is a new API to help end users view available destinations and query them to find JMS statistics such as active queue count, queue depth, number of messages etc.
有一个新的API可以帮助最终用户查看可用的目的地（destinations）并对其进行查询以得到JMS统计信息，如活动队列数量、队列深度及消息数量等等。
The health Monitoring widget, shown in Figure 2, is a new widget that aggregates health information for system applications, topology, user applications, messaging, and queue depth.
如图2所示的HealthMonitoring小部件是一个新的小部件，它聚合系统应用程序、拓扑、用户应用程序、消息和队列深度的运行状况信息。
In our simple example, since the server process is a CICS transaction, simply having multiple copies of the server transaction running in multiple CICS regions would keep the queue depth very low.
在我们给出的简单示例中，由于服务器进程是一个CICS事务，直接在多个CICS区域中运行多个服务器事务副本就可能将队列深度保持在很低的水平。
Discussions with the application group should be held to determine the maximum depth expected during peak periods, the size of the messages, and the anticipated duration on the queue.
关于应用程序组的讨论应该可以帮助确定在峰值期间预期的最大深度、消息的大小以及队列上的预期持续时间。
As the queue builds up, the depth is shown graphically as well as numerically.
随着队列的增大，将以图形和数字的方式显示队列深度。
Use the current depth of the queue.
使用队列的当前深度。
The output from this command should show that the queue has a current depth of 1 message, 'CURDEPTH(1)'
此命令的输出应该显示队列当前的深度为1条消息“CURDEPTH(1)”
The Queues TAB shows the status, depth, and utilization of queue points defined to your messaging engines, as shown in Figure 20.
Queues选项卡显示消息传递引擎定义的队列点的状态、深度和利用率，见图20。
The last step is crucial because when a queue is triggered on depth, WebSphere MQ disables triggering when the trigger is fired.
最后一步很关键，因为当一个队列在深度上被触发时，WebSphereMQ将在触发器触发后仅用触发机制。
As soon as the agent releases the input handle on its command queue, the queue manager detects that the command queue has a depth greater than zero, fires a new trigger event, and the agent restarts.
当代理释放器命令队列上的输入句柄时，则队列管理器检测到命令队列有一个大于0的深度，从而发出一个新的触发器事件，然后代理重新启动。
If issued at regular intervals during a normal production or test cycle, you can capture and track the number of messages that have been processed during that interval and the queue high depth.
如果在正常的生产或测试周期中按一定的间隔发出此命令，则可以捕获和跟踪在此期间已处理的消息数量和队列最高深度。
Please note that our server admin queue has a longer turn around time for responses, as the tickets tend to require more in depth evaluation.
请注意，我们的服务器管理队列中需要一个较长的的回应时间，由于问题表单往往需要进行更深入的评价。
应用推荐