Let's go a little deeper into the collected data. In our example, we see that
navigation to the OC Systems home page took over 3.7 seconds to complete. Let's
use RTI to figure out why.
At the bottom of the Analysis View you will see its 3 tabs listed: Overview, Deep
Dive, and Summary. These tabs
represent different visualizations or perspectives on the collected data. Let's
select Deep Dive to drill into the
performance of the ocsystems.com navigation, and you should see a page that
looks like this:
As you select Transactions in the upper Deep Dive tree, the lower chart will
automatically update to reflect that selection. We chose the 3.7 second
Transaction for ocsystems.com, and
so the chart below now represents the timeline of each web Event generated by
Internet Explorer to complete this Transaction. In this example, the chart is
showing both the application and the type of Web Event measured: “IE Navigation” shows there was a navigation event
made from Internet Explorer, while “Network-HTTP”
represents an HTTP network request made by the browser. The length of
each bar in the chart shows the total time (in seconds) of each Event, and you
can mouse-over any Event for more information.
Now let's use the Deep Dive tree to drill into the poorly performing
Transaction. For any Transaction where RTI has collected sub-Events, like
network requests for images, CSS files, etc., we can use the Deep Dive tree to
see each Event and identify why the overall Transaction was slow. Let’s select
ocsystems.com in the tree, and
then expand it by selecting the usual Windows [>] or [+] icon to the left of
the IE icon (this differs based upon the version of Windows). You should now
see something like this:
We sorted the Elapsed Time in descending order, to more easily identify which
Network HTTP Events took 1 second or more. By selecting multiple events of
interest and looking at the timeline chart, we can see that these Events ran in
parallel, which is why the overall performance of the Transaction was only 3.7
seconds instead of the sum elapsed time of each web Event.
RTI has shown us that our overall navigation to www.ocsystems.com took 3.7 seconds,
and we now know this slowness was caused by these multiple slow requests across
the network, most of which were images.
To further trace these web Events into the back-end of your system's web and
application servers, for example Tomcat, JBoss and Apache HTTPD, and to best
understand and to Deep Dive into the performance of your Web Application, please
see the additional documentation.
The Analysis View has one additional tab: a Summary view, which allows you to group the Transactions in
different ways to understand the bigger picture. For example, see the Summary View image.
 |  |  |
| 2.4.4. What Data Did RTI Collect? |  | 2.5. Diagnosing Performance Bottlenecks in Your Automated Testing |
