The queues output lists many queues. Monitor these queues closely:

  • SM_PropertyPoller: This queue contains client requests for property subscriptions and data to be sent to clients as responses to property subscriptions. For example, in the Global Manager, notifications are sent to clients through property subscriptions. So, the property poller queue contains notifications to be sent to clients.

  • SubscriberFE: This queue represents a connection the Global Manager server makes to another server, where the Global Manager server subscribes to information in another server. For example, there is a SubscriberFE queue for each underlying Domain Manager. For each queue, the first line provides name of the queue and the number of workers.


    Subscriber Front Ends like this one never have any workers, since they are not used as normal server queues.

    The second line provides the current size, and an exact maximum size. Also included is the total number of entries “processed.” To be exact, this is the total number of entries that were pulled from the queue.

    The next three rows provide averages. Each column reports values averaged over a different time interval: The last 3 minutes, 30 minutes, 300 minutes, and 3000 minutes. Each row reports a different value:

  • Size is the queue size, that is, the average of what “Current size” reports for this moment.

  • Flow is the number of queue entries processed, that is, the average of what “Current processed entries” reports.

  • Late is the delay between when an entry in a timer queue was scheduled to run and when it actually ran. The Late row is always all 0's for a server queue.

    Each of the averages listed in the Size, Flow, and Late rows have two fields separated by a sign (+ or -):

  • The first field is the average value of the variable over the appropriate period. The queue in the figure Global Manager queues information example has processed many entries -- almost 22,000 -- and once, even held 369 entries; but that was apparently an isolated peak some time in the past, since its average Size over all the reported intervals is 0: Most of the time, the queue is empty. On the other hand, the Flow value over the last 3 minutes is very close to the value for processed entries (21,843). If we look at this value averaged over longer and longer periods, we see that the longer the period, the smaller the value. This is what we would expect if the rate at which elements are flowing through this queue is roughly constant. Always keep in mind that Size grows and shrinks, while Flow can only grow.

  • The second field is the average rate of change in the first value, per second. In the example above, the Size is shrinking slowly: -0.0 indicates fewer than 0.01 entries per second. On the other hand, the Flow is increasing at a steady rate: between 0.05 and 0.06 entries per second (3.0 and 3.6 entries per minute) are flowing through this queue. Again, because Flow can only increase, the second field is always non- negative. Note that the rates are virtually the same across all time periods, which is consistent with the analysis in the previous paragraph that entries are flowing through at a slow, steady rate.