Once transaction profiles are transferred from an RTI collector (or reloaded from saved files) the RTI console will switch to the Transaction Profile perspective.  This perspective initially consists of of the following views:
  • Transaction Profile Snapshot – A tree that presents Business Transactions and methods discovered and measured by RTI. Each Transaction can be decomposed into its methods and nested transactions.
  • Collector Metric View (refer to Note below) – Chart displaying transaction performance over time, defaults to plotting application throughput and transactions per-minute, across the entire application as measured by RTI.
  • Platform Metric View (refer to Note below) – Chart displaying Platform Resource measurements. Defaults to average system and user CPU utilization or system load average.
Call Profiling perspective

Note

Chart visualizations accompany the Transaction Profile Tree when RTI is directly connected to an RTI host or to JBoss Operations Network.  So there are no metric view charts shown with the transaction profile when viewing a previously saved *.rtp file.

Note

Both collector and platform charts will attempt to plot measurements around the period of the current profiling information. Using the buttons above the charts, the time period can be adjusted to show the current data, which will be automatically refreshed, or any time period still available within the RHQ data repository.
The following information is displayed in the columns of the profile:
  • Name - the application, host, process, transaction, or method name.
  • Type - indicates if the profile row contains information about  a transaction (BTM) or a method.
  • Percent - the total time spent in this transaction or method and its children divided by the call count.
  • Call Count - the number of times this transaction or method was called.
  • Avg Time (Self) - the total time spent in this transaction, excluding time spent in its children, divided by the call count.
  • Min Time - the shortest time spent in this transaction or method.
  • Max Time - the longest time spent in this transaction or method.
  • Total Time - the total time spent in this transaction and its children.
The transaction profile is generally organized by the discovered transactions or methods, as seen in the left-most column. Each application transaction discovered by RTI is monitored independently--the profile information is aggregated for each separate transaction and presented in summary form.
You can sort the profile data by relevant columns to find the transactions and methods where performance is a problem.
You can drill down into a transactions profile call-stack tree to locate performance bottlenecks. The slowest path through the call-stack is marked by the light red markers.
Transaction Profile Snapshot view, expanded to follow slowest path
You can reset the profiling data back to "zero" using the Reset button (). If you reset before a test run you can isolate the profiling information to just that test, rather than every transaction seen so far.
Some transactions will require more elaborate analysis than just transaction profiling. You can start a deep-dive trace from a transaction profile by using the Enable Transaction Tracing button (). See 2.3 Deep-Dive Performance Diagnostics for more information.
You can change the contents and organization of the tree using the Display Mode button () as described above.
Most of these operations are available from the context menu by right-clicking in the transaction profile.
Lightweight Profile view context menu


loading table of contents...