• Effect of processing rates on queue depth.

    处理速率对队列深度的影响。

    youdao

  • And queue depth in the agent command queue changes from zero to one.

    且代理命令队列中的队列深度从0变为1。

    youdao

  • The queue depth exceeds the threshold set by TRIGDEPTH; a trigger fires.

    队列深度超过TRIGDEPTH设置的阈值时,触发器触发。

    youdao

  • The minimum queue depth shows how shallow the measurement object pool got.

    最小队列深度显示了度量对象池有多浅。

    youdao

  • When the queue depth is displayed, it does indeed contain exactly 800 messages.

    但队列深度显示时,它的确正好包含800条消息。

    youdao

  • To keep the queue depth low, the server process would have to run at a higher rate.

    为了保持队列深度值较低,服务器进程必须以更高的速率运行。

    youdao

  • As noted earlier, the queue manager disables triggering when a trigger is fired, based on queue depth.

    如前所述,当触发器触发后,队列管理器基于队列深度禁用触发机制。

    youdao

  • This sequence of events repeats each time the queue depth builds beyond the threshold configured in TRIGDEPTH.

    每当队列深度超过 TRIGDEPTH中配置的阈值时,这个事件序列都会重复。

    youdao

  • If the queue depth is high, assume that the application is not healthy or able to cope with the rate of messages.

    如果队列深度比较高,则假定应用程序不健康或不能够处理消息的速率。

    youdao

  • When you evaluate queue depth requirements, message processing rates are just as important as peak message volumes.

    当评估队列深度要求时,消息处理速率和峰值消息量同样重要。

    youdao

  • Here, you are inquiring on the current and maximum queue depth, the maximum message length, and the value of QDEPTHHI.

    这里,您查询的是当前和最大队列深度、最大消息长度、以及QDEPTHHI的值。

    youdao

  • 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对象正在排队等候审计线程处理。

    youdao

  • 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.

    请确保为这个队列定义的最大队列深度对于存储消息来说足够大,并且对它进行监视以确保不会超过最大深度。

    youdao

  • 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统计信息,如活动队列数量、队列深度及消息数量等等。

    youdao

  • 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小部件是一个新的小部件,它聚合系统应用程序、拓扑、用户应用程序、消息和队列深度的运行状况信息。

    youdao

  • 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区域中运行多个服务器事务副本就可能将队列深度保持在很低的水平。

    youdao

  • Queue depth events could be used to initiate configuration changes.

    队列深度事件能够用于发起配置更改。

    youdao

  • Queue depth events could be used to initiate configuration changes.

    队列深度事件能够用于发起配置更改。

    youdao

$firstVoiceSent
- 来自原声例句
小调查
请问您想要如何调整此模块?

感谢您的反馈,我们会尽快进行适当修改!
进来说说原因吧 确定
小调查
请问您想要如何调整此模块?

感谢您的反馈,我们会尽快进行适当修改!
进来说说原因吧 确定