Overview¶
Global menu points to consolidated statistics.
Details menu points to per-request-type statistics.
Note
You can use the -ro option to generate reports from a truncated simulation.log file, for example when the run was interrupted (Ctrl+C or process killed).
Note that the component in charge of logging into the simulation.log file uses a buffer, so last data might be missing if you forcefully interrupt.
See Configuration page.
Overall Simulation charts¶
Most of those charts are available for both the overall simulation report and for per request/group charts.
Indicators¶
This chart shows how response times are distributed among standard ranges. The right panel show number of OK/KO requests.
Note
these ranges can be configured in the gatling.conf file.
The top panel shows some standard statistics such as min, max, average, standard deviation and percentiles globally and per request.
Note
these percentiles can be configured in the gatling.conf file.
Note
If your scenario contains groups, this panel becomes a tree : each group is a non leaf node, and each request is a descendant leaf of a group. Group timings are by default the cumulated response times of all elements inside the group. Group duration can be displayed instead of group cumulated response time by editing the gatling.conf file.
The bottom panel shows some details on the failed requests.
Active users over time¶
This chart displays the active users during the simulation : total and per scenario.
“Active users” is neither “concurrent users” or “users arrival rate”. It’s a kind of mixed metric that serves for both open and closed workload models and that represents “users who were active on the system under load at a given second”.
It’s computed as:
(number of alive users at previous second)
+ (number of users that were started during this second)
- (number of users that were terminated during previous second)
Response time percentiles over time¶
This charts displays a variety of response time percentiles over time, but only for successful requests. As failed requests can end prematurely or be caused by timeouts, they would have a drastic effect on the percentiles computation.
Requests per second over time¶
This chart displays the number of requests sent per second over time.
Responses per second over time¶
This chart displays the number of responses received per second over time : total, successes and failures.
