How to use the flow analysis to find further performance problems
DoinaKlinger 120000NXW5 Visits (2077)
In a previous blog post, we have looked into the web tools that are available in IIB v9.0 to analyze the performance of the flows and how the tools can be best used to identify why a flow message rate is low or dropping.
See previous posts on how to enable these views.
Problem: CPU usage is high or increasing
This might not be a problem by itself, rather a consequence of running at a high rate.
In this case, you might want to order the Nodes table by Average Elapsed time to find out the node that takes most of the time and determine why the time is high. It may be due tp a problem with another application or service.
Select Total number of backouts , possibly Total Number of Errors Processing Messages, Total Number of Messages with Errors to check if there is a correlation.
Check the node types in the Nodes Table and verify if the optimizations for each node type have been applied.
You might want to check Average Elapsed Time/Invocation, Average CPU Time/Invocation, Total CPU Time, Total Elapsed time, Number of Threads in Pool, Times Maximum Number of Threads Reached and see whether the flow is CPU intensive.
Check Total Number of Backouts and then analyze the connected flows in a different browser tab.
There may not be sufficient instances of a flow to allow processing to proceed at the required rate. Particularly when a flow is running slow for example. Check Number of Threads in Pool and Times Maximum Number of Threads Reached. Look to see how many instances are defined for the message flow and whether they are all being used. This should tell you whether the peak number of threads is constantly in use.
The flow analysis tools from IIBv9.0 are very rich and flexible. They provide a variety of ways of examine the performance of your flows.