90th percentile is missing on Gatling report

Gatling (Open-Source)
1

used the config below, updated the same on gatling.config.

charting {
  #noReports = false       # When set to true, don't generate HTML reports
  #maxPlotPerSeries = 1000 # Number of points per graph in Gatling reports
  #useGroupDurationMetric = false  # Switch group timings from cumulated response time to group duration.
  indicators {
    #lowerBound = 800      # Lower bound for the requests' response time to track in the reports and the console summary
    #higherBound = 1200    # Higher bound for the requests' response time to track in the reports and the console summary
    percentile1 = 90      # Value for the 1st percentile to track in the reports, the console summary and Graphite
    #percentile2 = 75      # Value for the 2nd percentile to track in the reports, the console summary and Graphite
    #percentile3 = 95      # Value for the 3rd percentile to track in the reports, the console summary and Graphite
    #percentile4 = 99      # Value for the 4th percentile to track in the reports, the console summary and Graphite
  }
}
1 Like
2

hi there, nice catch :slight_smile: I just update some information for nicer look
Original Gatling.conf indicators content:

indicators {
      #lowerBound = 800      # Lower bound for the requests' response time to track in the reports and the console summary
      #higherBound = 1200    # Higher bound for the requests' response time to track in the reports and the console summary
      #percentile1 = 50      # Value for the 1st percentile to track in the reports, the console summary and Graphite
      #percentile2 = 75      # Value for the 2nd percentile to track in the reports, the console summary and Graphite
      #percentile3 = 95      # Value for the 3rd percentile to track in the reports, the console summary and Graphite
      #percentile4 = 99      # Value for the 4th percentile to track in the reports, the console summary and Graphite
    }

After workaround:

indicators {
      #lowerBound = 800      # Lower bound for the requests' response time to track in the reports and the console summary
      #higherBound = 1200    # Higher bound for the requests' response time to track in the reports and the console summary
      #percentile1 = 50      # Value for the 1st percentile to track in the reports, the console summary and Graphite
      #percentile2 = 75      # Value for the 2nd percentile to track in the reports, the console summary and Graphite
      percentile3 = 90     
      #percentile4 = 95      # Value for the 3rd percentile to track in the reports, the console summary and Graphite
      #percentile5 = 99      # Value for the 4th percentile to track in the reports, the console summary and Graphite
    }
3

Please describe what you think is not working.

4

I think the 90th percentile is not there by his mean, is this intended to remove in 3.10.3 ? @slandelle

5

Honestly, I really have no idea what you mean.

These configuration options let you override the default percentiles plotted in the charts and used for the assertions, eg with the above config:

Capture d’écran 2024-01-17 à 22.59.22
Capture d’écran 2024-01-17 à 22.59.22684×760 54.9 KB

6

hi @slandelle sorry for not read things carefully.
.
OP means that Gatling originally has 90th Percentile set up by default, and I thought the same too. So it leads to his question is that 3.10.3 version remove it by accident or something.
.
But I have checked on 3.9.5 this morning, 90th Percentile is not set by default.
This question can be closed I think.

7

I don’t think we’ve ever changed the default values. See Gatling 3.3: gatling/gatling-core/src/main/resources/gatling-defaults.conf at 3.3 · gatling/gatling · GitHub

So I don’t know what @Banu meant.

8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.