This report summarizes the success of
transactions in the run, graphs the response trend of each transaction
during a specific sample interval, and shows the transaction throughput.
This report graphs sample intervals within a run. You
set the Statistics sample interval value in
the schedule, as a schedule property.
Overall page
The Overall Transaction Rate graph
shows the average elapsed time for all transactions during a specific
sample interval.
Elapsed time is the actual time spent
within the transaction container. If you have set staged loads in
the schedule, this graph also delineates the stages with time range
markers, in various colors, at the top.
The table under the graph
lists the following information:
- The average elapsed time for all transactions in the entire run.
- The standard deviation of the elapsed time. The
standard deviation tells you how tightly the data is grouped about
the mean. For example, System A and System B both have an average
elapsed time of 12 ms. However, this does not mean that the elapsed
times are similar. System A might have elapsed times of 11, 12, 13,
and 12 ms. System B might have elapsed times of 1, 20, 25, and 2.
Although the mean time is the same, the standard deviation of System
B is greater—and the elapsed time is more varied.
- The longest transaction in the entire run.
- The shortest transaction in the entire run.
- The average net server time for all transactions in the entire
run.
- The standard deviation of the net server time.
- The longest net server time in the entire run.
- The shortest net server time in the entire run.
Elapsed Time vs. Time page
The Elapsed Time
vs. Time graph shows the average response of each transaction during
a specific sample interval. Each transaction is represented by a separate
line. If you have set staged loads in the schedule, this graph also
delineates the stages with time range markers, in various colors,
at the top.
The table under the graph lists the following information
for each transaction:
- The minimum elapsed time for the entire run.
- The average elapsed time for the entire run. This is similar to
the graph, but the information in the table is the average for the
entire run rather than the average per sample interval.
- The standard deviation of the average response time.
The standard deviation tells you how tightly the data is grouped about
the mean. For example, System A and System B both have an average
response time of 12 ms. However, this does not mean that the response
times are similar. System A might have response times of 11, 12, 13,
and 12 ms. System B might have response times of 1, 20, 25, and 2.
Although the mean time is the same, the standard deviation of System
B is greater—and the response time is more varied.
- The maximum elapsed time for the entire run.
- The rate, per second, at which the transaction was completed.
- The number of attempts for the transaction.
Net Server Time vs. Time page
Net server time
for a transaction is a measured time of interactions with the server.
Typically, this does not include think times or Rational® Performance Tester processing.
The server interaction calculation is protocol specific. For example,
in HTTP protocol, the net server time is exactly the sum of all page
response times. The elapsed time (wall clock time) includes think
time and other RPT processing overhead
Transaction Throughput Tab
These line graphs
provide an overview of the transaction frequency and the number of
users that are adding load, both over the course of a run.
- The Transaction Hit Rate graph shows the overall rates for starting
and completing transactions during a specified sample interval. If
you have set staged loads in the schedule, this graph also delineates
the stages with time range markers, in various colors, at the top.
The summary table under the graph lists the transaction rate per second
and the number of transactions that were completed for the entire
run.
- The User Load graph shows the number of active users and the number
of users that completed testing over the course of the run. The summary
table under the graph lists the number of active users, the number
of users that completed testing, and the total number of users for
the latest sample interval.