•
Active Time – It represents the sum of the active time of all virtual testers. The active time of a virtual tester is the time that the virtual tester spent thinking (including Figure 8.5. Command status reportdelays after the virtual tester’s first recorded command), executing commands, and waiting for responses.
•
Inactive Time – The sum of the inactive time of all virtual testers and test scripts.The inactive time of a virtual tester is the time before the virtual tester’s first emulation command (including the overhead time needed to set up and initialize the run), and possibly interscript delay (the time between the last emulation command of the previous test script and the beginning of the current test script).
•
Passed Commands – The total number of passed send commands, that is, com-mands that send virtual tester input to the server.•
Failed Commands – The total number of failed send commands, that is, commands that send virtual tester input to the server.•
Passed Responses – The total number of responses to send commands that were matched by passing receive commands. This is not the same as the total number of expected receive commands because a response may be matched by an arbitrary number of receive commands. A response is considered expected if all receive commands used to match it have an expected status.•
Failed Responses – The total number of responses that were matched by failing receive commands. This is not the same as the total number of unexpected receive commands because a response may be received by an arbitrary number of receive commands. A response is considered unexpected if any receive commands used to match it have an unexpected status because send commands and responses in a test script do not necessarily have a one-to-one correspondence. To illustrate, an HTTP script may issue one send command. The total of passed commands plus failed commands often does not equal the total of passed responses plus failed Figure 8.6. Command usage reportresponses (http_request) and receive multiple responses to the send (http_header_recv and one or more http_nrecv commands).
•
Average Throughput – Four measurements of average throughput are provided:passed command throughput, failed command throughput, passed response throughput, and failed response throughput. This represents the throughput of an average virtual tester.
•
Time Spent Waiting – The total time spent waiting for responses, given both in seconds and as a percentage of active time. The time spent waiting is the elapsed time from when the send command is submitted to the server until the server receives the complete response. The time that an http_request spends waiting for a connection to be established is counted as time spent waiting.•
Time Executing Commands – The total time spent in executing commands on the agent computer. This measurement is provided both in seconds and as a percent-age of active time. The time spent executing VU emulation commands that access an SQL server is defined as the elapsed time from when the SQL statements are submitted to the server until these statements have completed.•
Time Spent Thinking – The total time spent thinking, both in seconds and as a percentage of active time. The time spent thinking for a given command is the elapsed time from the end of the preceding command until the current command is submitted to the server. This definition of think time corresponds to that used during the run only if the Test Script Services (TSS) environment variable Think_def in the test script has the default LR (last received), which assumes that think time starts at the last received data time stamp of the previous response. If any VU emulation commands are executed that access an SQL server, the command usage report includes:•
Rows Received – Number of rows received by all reported sqlnrecv commands.•
Received Rows/Sec – Average number of rows received per second. Derived by dividing the number of rows received by the active time.•
Average Rows/Response – Average number of rows in the passed and failed responses. Derived by dividing the number of rows received by the number of passed and failed responses.•
Average Think Time – Average think time in seconds for sqlexec and sqlprepare statements only.•
Avg Execution Time – Average time in milliseconds to execute an sqlexec or DCOM method call command. Derived by dividing the time spent on sqlexec commands by the number of sqlexec commands.•
Avg Preparation Time – Average time in milliseconds to execute an sqlprepare command. Derived by dividing the time spent on sqlprepare commands by the number of sqlprepare commands.If any HTTP emulation commands are executed that access a Web server, the command usage report includes:
•
Passed HTTP Connections – Number of successful HTTP connections established by all reported http_request commands.•
Failed HTTP Connections – Number of HTTP connection attempts that failed to establish a connection for all reported http_request commands.•
HTTP Sent Kbytes – Kilobytes of data sent by reported http_request commands.•
HTTP Received Kbytes – Kilobytes of data received by reported http_nrecv and http_recv commands.•
HTTP Sent Kbytes/Sec – Kilobytes of data sent per second. Derived by dividing the kilobytes of data sent by all recorded http_request commands by the active time.•
HTTP Recv Kbytes/Sec – Kilobytes of data received per second. Derived by dividing the kilobytes of data received by all recorded http_nrecv and http_recv commands by the active time.
In document
Integrated Approach To Web Performance Testing - A Practitioner's Guide (2006).pdf
(Page 196-199)