Improving IBM WebSphere MQ Transport Performance

This topic is part of Guidelines for Siebel EAI Tuning.

The performance of an IBM WebSphere MQ queue is highly dependent on the disk performance of the queue manager computer and the layout of the queue's files on the disk. Test your queue with stand-alone utilities so that you have an upper boundary for the performance that can be expected in a live application.

To achieve higher throughput, consider the following options:

• Run multiple MQ Receiver tasks. Run multiple MQ Receiver tasks in parallel on the same computer or across several computers. The optimal number of MQ Receiver tasks depends on the transaction type.

  Note: This guide refers to MQ Receiver, where the actual Siebel Server component that you are using might be MQSeries Server Receiver (alias MqSeriesSrvRcvr) or MQSeries AMI Receiver (alias MqSeriesAMIRcvr).

  The default number of MQ Receiver tasks is 1. You can set this to 10 or more, depending on the nature of your transactions and on available server capacity.

  Adding MQ Receivers is generally most helpful for handling CPU-bound transactions, where the dequeuing rate is low and MQ contention is not experienced.

  Sometimes contention is still experienced after adding MQ Receiver tasks, such as when multiple MQ Receivers connect to the same MQ queue manager or queue. See the next item for more information.

• Run multiple MQ queue managers. If you experience diminishing returns from adding MQ Receiver tasks, then you might benefit from running additional MQ queue managers. Doing so can help to reduce contention of MQ resources stored in physical folders on disk.

• Turn off persistent queuing if it is unneeded. Performance issues for non CPU-bound transactions or for persistent queuing are often related to MQ contention, which is not helped by adding receivers. If you do not require persistent queuing, then turn it off.

  Persistent queuing is significantly slower than normal queuing for WebSphere MQ. If you do not use this feature, however, then messages will be lost if the queue manager goes down.

• Set Maximum Number of Channels parameter. Set the Maximum Number of Channels parameter in the WebSphere MQ queue manager to be greater than or equal to the maximum number of simultaneous clients that you have running.

In addition, you can take specific actions to improve WebSphere MQ Transport performance for outbound and inbound transports, as detailed in this topic.