As Gatling runs and executes requests, several timings are recorded, which make up the basis of all forms of reporting in Gatling: console, HTML reports, etc…
At a given second, active users are computed as:
- the number of active users at the previous second
- + the number of users who started during this second
- - the number of users who finished during the previous second
The response time is the elapsed time between the instant a request is sent and the instant the complete response is received:
- The beginning of the request’s sending is the instant when the connection to the target host has been established or grabbed from the pool.
- The end of the response’s receiving is the instant when the whole response (status, headers and body) has been received by Gatling
The counts are the number of group executions, not the sum of the counts of each individual request in that group.
The response time of a group is the cumulated response times of each individual request in that group.
When dealing with embedded resources (inferred or explicitly set), the behaviour is slightly different : as resources are fetched asynchronously, the cumulated response time for embedded resources starts from the beginning of the first resource request to the end of the last resource request.
The cumulated time of a group is the elapsed time from the start of the group’s first request to the end of the group’s last request, including pauses. Groups’ cumulated time are only reported in the “Cumulated response time” chart.