1. Capture a Transaction Profile Snapshot and find slow transactions as described above.
  2. Choose slowest one or few transactions, and apply Deep-dive trace for 5 minutes or a few transactions.
  3. Exercise your application for 5 minutes to collect deep-dive trace information.
  4. Transfer the deep-dive performance data. Remember to collect RTI trace data from all collectors involved with executing the transaction.
  5. Sort by decreasing Elapsed Time to find slowest transaction.
  6. Focus On the slowest (top) transaction to deep-dive into its constituent events.
  7. Use either the expansion widget or right-click and choose Focus On Transaction from the context menu.
  8. Follow slowest path to track bottleneck. The slowest path through the transaction call-tree is indicated by the light red percentage bars.
  9. Switch to Flat mode, then Sort to find slow component events.
  10. Use the Transaction Event Summary table to find component events with high call counts and/or long execution times:
  11. Pick a suspicious component event and Filter to see all similar events:
  12. Examine filtered transaction list to see if suspicious event is out of normal range:

loading table of contents...