Work breakdown costs

To successfully optimize an application it is essential you collect a clear picture of how much time each discrete piece of activity is costing. The easiest way to do this is to use the FTM level 1 trace to collect an elapsed time breakdown for all mappers, actions, transitions and events. You will then need to evaluate this breakdown to identify areas that are more costly than expected and use this to drive focused reviews followed by further testing of code and model changes. When analyzing the work breakdown, you must of course consider than some types of activity take more time than others, typically inbound mappings and outbound mappings are costly including events, transitions and actions directly related to outbound mappings. You should also factor in any other activity in your process that you anticipate to be costly when evaluating FTM level 1 trace. In addition to FTM level 1 trace, database tools such as db2top can be used to capture and analyze the SQL workload and IBM® Integration node(broker) statistics can be used to supplement the FTM trace.

If you have a complex application it may also make sense to break it up into smaller parts and evaluate each one individually.