Analyze the results
Understanding the final results after the simulation
Last updated
Understanding the final results after the simulation
Last updated
After your simulations have completed running, you will want to see how many requests went through, how many failed and other data related to the simulation.
You can find all of the data related to the simulation run in a well-organized manner on the Results page. Here, you will see a list of all the different simulation jobs with an overview of their results. The status of currently running tests are updated in real-time.
On this page, you can also stop an ongoing simulation job, delete an old job or restart a completed job. All of these can be done by clicking on the respective icons under the Operations column.
If you want to know about more detailed results for a specific job, you can do so by clicking on the folder icon under the Operations column. Once you click that, the detailed results for the specific job will be opened.
The results are divided into several tabs: Summary, Logs, State and Payload. Let's go through them one by one.
If you are sending more messages or connecting more clients than what your server could handle, every client is eventually going to wait for its turn to connect and send, thereby stretching the overall test duration. It is important to carefully tune timeout values in your template to handle this worst case, otherwise, the iteration will be marked as failed.