What factors impact the CPU consumption of MainView for Websphere MQ?

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    MainView for MQ


    MainView for WebSphere MQ


    What factors impact the CPU consumption of MainView for Websphere MQ? How can MainView for Websphere MQ be tuned to limit CPU consumption/usage?

    LP: MainView for WebSphere MQ




    Legacy ID:KA403824


    The CPU usage of MainView for WebSphere MQ is driven by the amount of monitoring activity requested and not how active the queue manager is. For example, the LQ view for a queue manager with 5000 local queues will use the same amount of CPU usage regardless of the level of activity within the queue manager itself.

    • BMC Software recommends that you set EXITOPT to use BPM=NO and CONNDISC=NO for better performance.    
      • BPM=[YES|NO] - indicates whether the product will build a queue name index and display statistics on a queue basis.
      • CONNDISC=[YES|NO] - indicates whether specified connect and disconnect calls will be traced
    • With MainView for WebSphere MQ, extra care should be taken when defining alarms, see Chapter 4 of the MainView for WebSphere MQ User Guide (Usage scenarios)
    • On most views, an object name is passed as a parameter to MainView for WebSphere MQ and to the Queue Manager (when the request is made).
    • Many view requests are issued for a queue manager with a large number of objects, care should be taken if auto-refresh is used.    
      • If the LQ view is issued for a queue manager with 10 queues then the queue manager will send back 10 messages.
      • If there are 5000 queues the queue manager will send back 5000 messages.
      • If the queue manager has 5000 queues and a user sets up LQ with auto-refresh this could amount to tens of thousands of MQGETs to satisfy the LQ view.
    • Every time History is collected, MainView for WebSphere MQ will issue view requests in the background for all MQ objects. This will occur at every IRRI interval (default of 15 minutes).    
      • If the Interval Recorder Interval (IRRI) is set too low this can also result in a large amount of MQGETs.
      • The customer can increase the IRRI value in BBPARM BBIISP00 to reduce the amount of history collection.
      • The user can also turn off selected history collection in QMPROF.
    • To operate and evaluate alarm definitions more efficiently, MainView Alarm Management arranges alarm definitions that are evaluated from the same data into evaluation sets. Each evaluation set can contain up to sixteen alarm definitions.    
      • The user does not control which alarm definitions are put into which evaluation sets. MainView Alarm Management does that automatically based on the data that the alarm definitions are accessing and evaluating.
      • Some products, including MainView for Websphere MQ use parameters and column filters to pre-filter data on some views. If the filter is present on these views, only data that matches that filter will be presented to MVI for alarm evaluation.
      • Alarms that use pre-filters should be run in separate evaluation sets. This is controlled by setting the UNIQUE AES parameter to YES.
    Related Products:  
    1. MainView for WebSphere MQ


    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles