Running Your Test from the Command Line

Once everything has been validated, it is time to start our load test. Best practices recommend using the JMeter command line.

The benefit that the command line has over the GUI is that it consumes fewer resources and gives more reliable results:

• The GUI management thread no longer disrupts injection.
• Many memory-intensive components in GUI mode are not active in CLI mode (such as View Results Tree).
• The listeners will no longer interrupt or interfere with the injection to refresh themselves (no more interruptions from graph updates and counters, for instance).

Here is the command line to execute JMeter:

     <JMETER_HOME>/bin/jmeter -n -t <Path + JMeter scripts file> -l <Results file path>/results.csv

• n: CLI mode (also called non-GUI mode in JMeter)
• l: Result file
• t: JMeter scripts file

Another interesting option is -J{name of the variable}={value of the variable}, which allows...