Why must JMeter run in non-GUI mode for real load tests?

Question

GUI works fine on my laptop. Why do all guides insist on -n -t for CI?

Aiko Tanaka · Accepted Answer

The GUI consumes ~30-40% of the JVM just rendering results. Under real load that skews every metric you measure — you end up load-testing JMeter, not your app. Non-GUI (-n -t plan.jmx -l result.jtl) frees the JVM and gives clean numbers. Analyze the .jtl afterwards.

jmeter -n -t plan.jmx -l result.jtl -e -o report/
# -n = non-GUI, -e = generate HTML report, -o = output dir

Why must JMeter run in non-GUI mode for real load tests?

1 answer