Configuration

This page explains how Gatling can be configured

Introduction #

Gatling can be configured and optimized in three ways:

• By the configuration files
• By command line options
• By $JAVA_OPTS environment variable

Configuration files #

Logback.xml

This file allows you to configure the log level of Gatling. For further information, you should have a look at Logback Documentation.

Gatling.conf

This file allows you to set configurable values for the Engine and the modules of Gatling; each value is described in the default configuration file.

If you don't specify an option in the configuration file, it will fall back to a default value. These values are also shown in the default configuration file.

Command Line Options #

Gatling can be started with several options listed below:

• -nr (--no-reports): Runs simulation but does not generate reports
• -ro <folderName> (--reports-only <folderName>): Generates the reports for the simulation in <folderName>
• -cf <fileName> (--config-file <fileName>): Uses <fileName> as the configuration file
• -df <folderName> (--data-folder <folderName>): Uses <folderName> as the folder where feeders are stored
• -rf <folderName> (--results-folder <folderName>): Uses <folderName> as the folder where results are stored
• -bf <folderName> (--request-bodies-folder <folderName>): Uses <folderName> as the folder where request bodies are stored

$JAVA_OPTS #

Default JAVA_OPTS are set in Gatling's launch scripts, if you want to override them, you'll have to edit these files and replace whatever value you'd like to change in JAVA_OPTS.

If you want to set additional JAVA_OPTS to Gatling, you can do so by defining the JAVA_OPTS before the gatling command:

~$ JAVA_OPTS="myAdditionalOption" bin/gatling.sh