Analyzing message flow performance

Measures of performance typically include product speed in terms of processing rate and response times, and resource usage in terms of the CPU and memory consumed. In order to assess the performance of an application, metrics are used to compare the actual performance with the required or expected performance, using measures such as the number of messages per second, elapsed time, CPU utilization, or CPU cost per message. You can use the message flow statistics and accounting data to assess the performance of your message flows and applications using some of these metrics, and to identify the message flows and nodes that might benefit from tuning to improve performance.

Message flow statistics for subflows are accumulated in the metrics for the top-level parent flow. For example, if a subflow contains an Input node, the number of message flow threads and any node-level additional instances from the subflow will be reported in the NumberOfThreadsInPool property of the statistics for the parent flow.

You can configure and start or stop the collection of statistics data, either by modifying the .yaml configuration file for the integration node or server, or by running the mqsichangeflowstats command. For more information, see Configuring the collection of message flow statistics by using a .yaml configuration file and Configuring the collection of message flow statistics by using the mqsichangeflowstats command.

You can view the collected statistics by using the web user interface, as described in Viewing message flow statistics and accounting data.

For information about how to see the current settings for message flow statistics collection, see Viewing message flow accounting and statistics data collection parameters by using the mqsireportflowstats command.

For troubleshooting information that includes guidance on dealing with performance issues, see Troubleshooting performance problems.