The following metrics are captured and displayed on the test run and reports pages of VPT.

Users (or virtual users) represents the number of threads performing actions as part of your test.

Started Users is the number of threads that have started for your test. Typically, a test starts with zero users and gradually ramps up to the configured user count as the test progresses. This count will increase as new unique users start.

Active Users are threads which are currently executing actions as part of the test. This count will fluctuate based on the structure of the script and test. As users are ramping up, the active user count will increase. If there is a ramp down in the script, the count will decrease as users stop performing actions.

Max Users is the maximum number of users running concurrently at any point in your test.

Transactions is the number of requests or samples sent to the target application during a test. This number can vary based on the structure of your test script.

The errors reported on the report page are errors received by JMeter from the target application. Errors typically fall into one of two categories: HTTP and Non-HTTP responses. HTTP-based errors correspond to typical HTTP error responses (client and server) from web-based services. Non-HTTP responses can cover other errors in network, configuration, and communication between VPT and the target application.

Error Count is the total number of errors encountered during the test.

Error Percentage is the percentage of the total samples, or requests, that result in an error. The Run Highlights on the report page shows the error percentage as the percent of total transactions that resulted in an error. The Error Status section of the report shows the error percentage for each unique response code as a percent of the total errors.

Response time is a measure of the amount of time between when VPT sends a request to the target application and when VPT receives a response from the target application. The response time of every request sent during a test is captured, and the average response time is calculated and shown as the test is running and after completion on the report page. The values are expressed in milliseconds, where 1,000 milliseconds are equal to one second.

Current Average Response Time is shown while the test is running. It represents the average response time for the requests received in the last 15 seconds. This gives you a better idea of whether the response times are increasing or decreasing during the test.

Overall Average Response Time is the average response time aggregated across all responses that have been received for a test.

The average throughput shows the average number of requests that are being sent to the target application per second during a test. = This is also denoted as TPS (transactions per second) throughout VPT.

Recent TPS is shown while the test is running. It represents the TPS for the last 15 seconds.

Overall TPS is the average throughput aggregated across the entire duration of the test.

The average bandwidth of a test is a measure of the amount of data received in responses from the target application. In VPT this is expressed in kilobytes per second unless otherwise noted.