JMeter Heap / JVM Sizing Estimator

JMeter Heap / JVM Sizing Estimator

Pick a starting -Xmx for injectors. Memory depends on threads, samplers, scripting, listeners, and response sizes. This tool gives a conservative first guess you should validate with GC logs.

Total threads

thr

Across the whole test (all engines)Injector engines

n

Distributed engines (not counting controller)

Heavy JSR223 / Groovy scripting Heavy listeners (View Results Tree) Large response bodies retained

Suggested -Xmx-

Threads / engine-

JVM flags-

Copy JVM flagsCopy shareable link

Heuristic only. Validate with GC logs. Prefer CLI mode and minimal listeners. See Best Practices and Remote Testing.

How to apply the flags

On the command line (example):

JVM_ARGS="-Xms512m -Xmx2048m" jmeter -n -t plan.jmx -l results.jtl

Or paste HEAP into the CLI Command Builder with the rest of the run flags.

Or set HEAP in your JMeter startup script / environment for the version you ship.

Practical tips

• Prefer CLI mode for load; GUI burns heap on rendering.
• Disable View Results Tree / Table during load tests.
• In distributed mode, size each engine for its share of threads.
• Controllers usually need less heap than injectors.

Related reading

• Best Practices
• Thread Calculator
• Remote Testing
• Listeners

Continue Learning

→

Next Practical Step

Size threads with the Thread Calculator, then re-check heap.

📖

Related Reference

Properties cheat sheet · Dashboard report

⚠

Common Mistakes

Raising -Xmx endlessly while View Results Tree is still enabled.

🔧

Troubleshooting

Still OOM? Reduce threads per engine, strip listeners, avoid saving response data.