Search⌘ K
Home
Courses
Performance Test Automation 101: Gatling, Lighthouse, & Jenkins

Understanding the Gatling Report

Learn how to analyze a Gatling report.

We'll cover the following...

In the previous lesson, we learned how to run the Gatling test script. In this lesson, we will understand the generated Gatling report.

The last line of the execution console output shows the HTML report path.

Shell
================================================================================
---- Global Information --------------------------------------------------------
> request count                                          2 (OK=2      KO=0     )
> min response time                                    476 (OK=476    KO=-     )
> max response time                                   1034 (OK=1034   KO=-     )
> mean response time                                   755 (OK=755    KO=-     )
> std deviation                                        279 (OK=279    KO=-     )
> response time 50th percentile                        755 (OK=755    KO=-     )
> response time 75th percentile                        895 (OK=895    KO=-     )
> response time 95th percentile                       1006 (OK=1006   KO=-     )
> response time 99th percentile                       1028 (OK=1028   KO=-     )
> mean requests/sec                                      1 (OK=1      KO=-     )
---- Response Time Distribution ------------------------------------------------
> t < 800 ms                                             1 ( 50%)
> 800 ms < t < 1200 ms                                   1 ( 50%)
> t > 1200 ms                                            0 (  0%)
> failed                                                 0 (  0%)
================================================================================
Reports generated in 0s.
Please open the following file: /Users/desktop/gatling-load-test/gatling-results/samplesimulation-20200531214559990/index.html

Global Information

This chart shows how response times are distributed among standard ranges. The right panel shows the number of OK/KO requests.

The top panel shows some standard statistics such as min, max, average, standard deviation, and percentiles globally and per request.

Request indicators range, and percentiles can be overridden using the following properties:

gatling.core.charting.indicators.lowerBound = 200
gatling.core.charting.indicators.higherBound = 800

gatling.core.charting.indicators.percentile1 = 50
gatling.core.charting.indicators.percentile2 = 75
gatling.core.charting.indicators.percentile3 = 90
gatling.core.charting.indicators.percentile4 = 95
widget

Individual HTTP request information can be viewed by clicking on the “Details” tab.

widget

Response time against Global RPS

This chart is only available when looking at the details for an individual request/group.

widget

Active Users along with the Simulation

This chart displays the active users during the simulation: total and per scenario.

“Active users” are neither “concurrent users” nor “users arrival rate”. It is a kind of mixed metric that serves for both open and closed workload models that represent “users who were active on the system under load at a given second”.

It’s computed as:

...