Table of content

• Timings in Gatling

We know that Gatling runs and executes requests, and it's then when several timings are recorded. Those timings recorded are the main parameters of Gatling's report. Such as the console or the HTML reports, or any other output file.

There are different types of parameters on which the report is generated. For example, Active Users, Requests, etc. Let us look one by one below:

Active Users :

In a given second, the number of active users is computed as follows:

• The active users at the previous second
• Plus the number of users who started during this current second.
• Minus the number of users who already finished during the previous second

Requests :

It may be noted that Response Time is the elapsed time between the instant a request is sent and the instant when the complete response is received.

The starting of the sending is the instance when the connection to the target host has been established or grabbed from the pool. And the end of the response's receiving is the instant when the whole response's status, headers, or the body has been received by Gatling.

Groups :

Let us talk about the three parameters here:

• Count: Counts are the number of group executions. It should not be confused with the sum of the counts of each individual request in that group.
• Response Time: The response time of a group is the cumulated response times of each individual request in that group.
• Cumulated Time: This is the total time between the group's first request and the last request including pauses also.

Recommended Readings

• Introduction to Gatling
• Scala for gatling
• Creating scenario in Gatling
• Running Gatling Test Script
• Gatling Plugins
• Assertions in Gatling
• Gatling Session
• Gatling HAR Analysis