Timings

Learn about all the recorded metrics: active users, response times and counts

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…

Active Users

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)

Requests

Response Time

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

Groups

Count

The counts are the number of group executions, not 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.

Duration

Group duration is the elapsed time between the instant a virtual user enters a group and the instant it exits.

Group duration is reported in the “Duration” charts.

Cumulated Response Time

Group cumulated response time is the time in a group when requests are flying: requests’ response time and resources start to end duration. In short, it’s the group duration minus the pauses.

Group cumulated response time is reported in the “Cumulated Response Time” charts.

Edit this page on GitHub