queue depth

You should not do anything with them, but it might be interesting for you to see the queue depth of some of the queues.

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

And if the queue depth had been set to the 5000 calculated earlier, it would have been exceeded within the first half an hour.

The work queue depth is the number of replications waiting to be processed by the cluster replicator.

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

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

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

Queue depth events could be used to initiate configuration changes.

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.

When multiple replicators are used, the cluster replication queue and work queue depth times are reduced.

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

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

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

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

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

The queue points current queue depth is displayed, as Figure 7 shows.

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

Effect of processing rates on queue depth