This report summarizes the validity of the run,
summarizes the data most significant to the run, shows the response trend
of the slowest 10 pages in the test, and graphs the response trend of each
page through time.
Overall tab
The Overall tab provides the following
information:
- A progress indicator that shows the state of the run.
- A bar chart showing the overall success of the run. The chart shows:
- The percent page element status code success for the entire run.
Page element success means that the response code verification
point passed for that request. If a request has no verification points, success
means that the server received the request and returned a response with a
status code in the 200 or 300 category, or an expected response with a status
code in the 400 or 500 category.
- The percent page status code success for the entire run.
Page
status code success means that the response code verification point
passed for the primary request. If a primary request has no verification points,
success means that the server received the request and returned a response
with a status code in the 200 or 300 category, or an expected response with
a status code in the 400 or 500 category.
- If the run contains page title verification points, the percentage that
passed.
- If the run contains response code or response size verification points,
the percentage that passed.
Summary tab
The Summary tab summarizes the data most
significant to the test run and lets you analyze a test’s final or intermediate
results at a glance.
The Summary tab displays the following Run
Summary information:
- The number of active and completed users. This number is updated during
the run.
- The elapsed time. This is the run duration, which is displayed in hours,
minutes, and seconds.
- Displaying results for computer: All Hosts.
You can see summary results for individual computers by clicking on the computer
name in the Performance Test Runs view.
- Status, which is the status of the run. This can be Initializing
Computers, Adding Users, Running, Performing
Execution History Data Transfer, Stopped,
or Complete.
The Summary tab displays the following Page Summary information:
- The average response time for all pages. Response time is
the sum of all page element response times (including the connect time and
inter-request delays).
- The maximum response time for all pages.
- The minimum response time for all pages.
- The total page attempts and the total page hits. A page attempt means
that a primary request was sent; it does not include requests within the page.
A hit means that the server received the request and returned
any response.
- If you have set page verification points, this tab shows a summary of
the page verification point results.
The Summary tab displays the following Page Element
Summary information:
- The average response time for all page elements. Response time is
the time between the first request character sent and the last response character
received.
- The total page element attempts and hits. An page element attempt means
that a request was sent. A hit means that the server received
the request and returned any response.
- The percent of verification points that passed.
- If you have set page element verification points, this tab shows a summary
of the verification point results.
If you have set transactions in your test, the Summary tab displays
the following Transaction information:
- The minimum, maximum, and average response time for all transactions. Response
time is the actual time spent within the transaction container.
- The total transactions started and the total completed.
Page Performance tab
The Page Performance tab shows
the average response of the slowest 10 pages in the test as the test progresses.
It enables you to evaluate the system's response for the test duration, as
well as after a test.
The bar chart shows the average response time of
the 10 slowest pages. Each bar represents a page that you visited during recording.
As you run the test, the bar chart changes, because the 10 slowest pages are
updated dynamically during the run. For example, the Logon page might be one
of the 10 slowest pages at the start of the run, but then, as the test progresses,
the Shopping Cart page might replace it as one of the ten slowest. After the
run, the tab shows the 10 slowest pages for the entire run.
The table,
under the bar chart, provides the following additional information
- The minimum response time for each page in the run. Response time is
the time between the first request character sent and the last response character
received.
- The average response time for each page in the run; that is, the same
information that is graphed.
- The maximum response time for each page in the run.
- The number of attempts per second to access each page. An attempt means
that a primary request was sent; it does not include requests within the page.
- The total number of attempts to access the page.
Response vs. Time Summary tab
The
Response vs. Time Summary tab lets you see the average response trend as graphed
through time. It contains two line graphs with corresponding summary tables:
- The line graph on the left shows the average response time for all pages
during the run. Each point on the graph is an average of what has occurred
during that interval. The table under the graph shows one number: the total
average response time for all pages in the run.
- The line graph on the right shows the average response time for all page
elements during the run. Each point on the graph is an average of what has
occurred during that interval. The table under the graph shows one number:
the total average response time for all page elements in the run. You set
the Statistics sample interval in the schedule, as
a schedule property.
Response vs. Time Detail tab
The Response vs. Time
Detail tab lets you see the response trend as graphed through time. Each page
is represented by a separate line.
The line graph shows the average response
of each page through time. The table under the graph contains the following
supplementary information:
- The minimum page response time for the run. Response time is
the time between the first request character sent of the primary request and
the last response character received; it does not include requests within
the page.
- The average page response time for the run (this is similar to the graph,
but the information in the table includes the entire run).
- The maximum page response time for the run.
- The rate of page attempts per interval for the most recent sample interval.
A page attempt means that the primary request was sent; it does
not include requests within the page. You set the Statistics
sample interval in the schedule, as a schedule property.
- The number of page attempts per interval.
Page Throughput tab
The
Page Throughput tab gives you an overview of the frequency of requests being
transferred per interval.
- The line graph at the left shows the page attempt rate and page hit rate
per interval for all pages. A page attempt means that the primary
request was sent; it does not include requests within the page. A hit means
that the server received the request and returned any response. The summary
table under the graph shows the total hit rates and counts for each page in
the run.
- The line graph at the right shows active and completed users over the
course of a run. The summary table under the graph shows the most recent sample
interval. You set the Statistics sample interval in
the schedule, as a schedule property.
Server Health Summary tab
The
Server Health Summary tab lets you see an overall indication of how well the
server is responding to the load.
- The bar chart on the left shows the total page attempts, page hits, and
status code successes for the run. The table under the chart shows the same
information.
A page attempt means that a primary request was
sent; it does not include requests within the page.
A hit means
that the server received the request and returned any response.
A success means
that the response code verification point passed for that request. If the
request has no verification points, a success means that the server received
a request and returned a response where the status code was in the 200 or
300 category, or an expected response in the 400 or 500 category.
- The bar chart on the right shows the total page element attempts, page
hits, and status code successes for the run. The table under the chart shows
the same information.
Server Health Detail tab
The Server Health Detail tab
provides specific details for the 10 least successful pages
- The bar chart shows the 10 least successful pages
- The summary table under the chart shows, for all pages, the number of
attempts, hits, and successes in the run, as well as the attempts per second
during the run.
An attempt means that a primary request was
sent; it does not include requests within the page.
A hit means
that the server received the request and returned any response.
A success means
that the response code verification point passed for that request. If the
request has no verification point, a success means that the server received
a request and returned a response where the status code was in the 200 or
300 category, or an expected response in the 400 or 500 category.