Throughout VPT you will see various data visualizations which show how certain key performance indicators (KPI) change over the duration of the test. These graphs make it easier to find breaking points and other anomalies and correlate them with events during the test.

The Load Chart can be seen as the test is running as well as on the report page at the conclusion of the test. This graph shows the number of active users shaded in blue, along with the throughput in hits (or requests) per second in green and the number of errors in red. The intention of this graph is for you to easily see the how the application is responding to increased load. Typically, the hits per second should increase proportionally to the number of users (of course, this depends on the script and test). If you see large fluctuations in hits or a rapid increase of errors, your target application could be failing or reaching a breaking point.

The Response Chart shows the number of users for the duration of the test like the Load Chart, but it also displays the minimum, maximum, and average response times throughout the test. This can give you an idea of how long your users are waiting for responses from your application while it is under load.

The Error Status table is populated with any errors your test encounters errors from the target application. The table lists all the unique error types and displays the response code as well as the response message. The table also displays the count of each error and the percentage each error accounts for. This can help you diagnose the cause for errors while the test is running or after completion.

The Statistics table gives you a detailed breakdown of metrics per sampler for your test. Each sampler in your script will be listed in the table, and you will be able to see metrics like successes (OK), failures (KO), average response time, bandwidth, throughput, and more. This information can help you identify which sections of your test are experiencing higher than normal response times or errors. This table will vary based on the configuration of your test script.

The Top Slow Responses table lists the top 20 slowest transactions during the test. It is broken down into the top 10 slowest successful transactions and the top 10 slowest failed transactions. This can give you an idea of the worst-case response times users may experience using your application while it is under load. It can also help identify problem areas of your application.