Glossary of Terms
Basic Terms
Vuser: Entity that simulates the actions of a real user. Script : Step by step actions that define a flow. Transaction: An action(s) performed in a step. Pacing: The time between two consecutive flows. Ramp: Allows scaling of users up and down at the start and end of the test. Action/Hour: Number of flows per hour. Think Time: The time between two transactions. Use of this think time is to simulate real time scenario. We can limit the think time or we can modify the think time. Parameters : - static: Input data for the script. - dynamic: session parameters
Analysis Summary
Header Time Range: This date is, by default, in the European format of dd/mm/yy (30/8/2008 for August 30, 2008). Scenario Name: The filepath to the lrs file. Results in Session: The filepath to the lrr file.
Statistics Summary
Maximum Running Vusers: This number is usually smaller than the number of vusers specified in run-time parameters because of ramp-up time (shown in the Running Vusers graph) and processing delays. Total Throughput (bytes):
It displays the total raw amount of bytes that the Vuser clients received as a result of the hits on the web server during load testing. Average Throughput (bytes/second): This could be shown as a straight horizontal line in the Throughput graph. Because network bandwidth is specified in the number of bits per second, dividing this by 8 yields the average bandwidth used, which is less useful than momentary peak bandwidth usage shown in the Throughput graph. Total Hits: The total amount of load Vusers generate, in terms of the number of hits to all web servers. It displays the number of hits made on all Web servers by Vusers during the load test.
Average Hits per Second: This could be shown as a straight horizontal line in the Hits per Second graph. It represents the average number of hits made on all Web servers by Vusers during each second of the load test.
Transaction Summary
Transactions: Total Passed is the total of the Pass column. The number of transactions Passed and Failed is the total count of every action defined in the script, multiplied by the number of vusers, further multiplied by the number of repetitions, and also multiplied by the number of iterations. The numbers to the left of the Pass column are the number of seconds. The Minimum, Average, Maximum columns are illustrated in the Transaction Performance Summary graph. Average Response Time Transaction Name Minimum: This is the fastest time Average: This is the arithmetic mean Maximum: This is the slowest time Std. Deviation:
"Std." is an abbreviation of the word "Standard", so called because the mathematical technique used to calculate it (taking the square root of the sum of squared numbers) "standardizes" (makes absolute) both positive and negative deviations from the average. The larger the std. deviation, the more "dispersed" or volatile the values are around the average. The standard deviation statistic is used to determine whether the difference between two runs could have been caused by pure chance rather than changes in coding or configuration settings. 90 Percent: Indicates the maximum response time for ninety percent of the transactions. Median: This is not shown in the Controller screen during a run because it is calculated from a list of all values the middle value from among all measurements ranked by value.
Pass: This is the count of iterations which were successful with no errors. Fail: This is the count of iterations which ended with an error Stop: This is the count of iterations which were halted HTTP Responses Summary HTTP 200 ("OK") is considered successful. HTTP 302 highlights a redirection ("Moved Temporarily"), a normal event. HTTP 404 is a "resource not found" error. HTTP 500 is a "server busy" error HTTP 503 is an authentication denial.
Graph reports
Running Vusers
This line graph shows the impact of Ramp-Up and Ramp-Down specified for runtime. This also shows the time when Errors begin to occur during the test run. The time when the Number of Vusers peaks and when it begins to drop off is the "steady state" period of the run.
Average Transaction Response Time
This line graph is used to determine whether performance is within acceptable minimum and maximum transaction performance time ranges expected of the system. It displays the average time taken to perform transactions during each second of the load test. Unlike the Summary Report, only Transaction End Status of Passed are included (Failed transactions are filtered out by default).
Transactions per Second
This line graph helps you determine the actual load imposed by each transaction action at various spans of time throughout a run. Each line displays the number of transactions performed both passed(successful) and failed(unsuccessful) transactions.
Total Transactions per Second
This graph helps you determine the actual total transaction load on your system at any given moment in time. This line chart displays the total of all transaction actions performed during each second of a load test. An additional line is used to display the total number of Failed (unsuccessful) transactions.
Transaction Summary
This bar graph displays, by transaction action, how many transactions passed, failed, stopped, or ended with errors.
Transaction Performance Summary
This bar chart displays the minimum, average, and maximum response time for each transaction action in the load test.
Transaction Response Time Under Load
This XY graph illustrates how the Number of Vusers impacts Response Time. Typically, individual response times follow an exponential curve up as servers strain to process more Vusers. A flat horizontal line means that response time does not vary, usually because the system has enough (or too much) capacity.
Hits per Second
The one line on this graph helps you evaluate the amount of load Vusers generate, in terms of the number of hits to all web servers. It displays the number of hits made on all Web servers by Vusers during each second of the load test.
Hits Summary
This pie chart displays the number of hits made on the Web server by Vusers. This graph helps you evaluate, in terms of the number of hits, the amount of load Vusers generate.
Throughput
This line chart helps you to evaluate the amount of load Vusers generate on network resources. It displays the raw amount of bytes that the Vuser client received each second as a result of the hits on the web server during load testing.
Throughput Summary
This pie chart illustrates values in the Total Throughput (bytes) presented in the Summary report.
Connections per Second
This line graph displays the number of HTTP & HTTPS Connections requested of all web servers. The graph displays different lines for New Connections and Connection Shutdowns.
SSLs Per Second
This line graph only appears when web apps use HTTPS from servers with SSL certificates installed, commonly associated with login transactions which require added security. This line graph displays the number of New and Reuse Sessions processed per second.
UNIX CPU Util
Each line on this graph displays for each Linux GH9 server the percent of CPUs are busy. It is obtained using the vmstat or sar command. The maximum is 400 for a 4 CPU machine.
UNIX Avg Load- Last 60 sec (one minute)
Background monitoring (rstatd and rup) consumes additional scenario time.
UNIX Paging rate
Each line on this graph displays for each Linux GH9 server the rate pages are swapped in and out of memory.
Apache CPU Usage
Each line on this graph displays the number of CPU Resource used on an individual web server. Differences in usage among web servers may indicate issues with the load balancing method or configuration differences among web servers.
Apache Hits/sec
Each line on this graph displays the number of hits coming through an individual web server each second.
Apache KBytes Sent/sec
Each line on this graph displays the number of raw Kilobytes coming through an individual web server, similar to the UNIX netstat command. At rest, each server averages 0.150 of keep-alive traffic.
Web Page Breakdown
This graph lists the average download time for each transaction action.
Page Component Breakdown
This pie chart shows how much each component is a percentage of the sum of Average download time (in seconds).
