Why it is recommended to run load test in non gui mode in jmeter

user_5488183 0
Viewed 296

I'm monitoring the connect time and latency to connect from jmeter machine while running in GUI mode and that is in within acceptable limit.

Should we strictly follow non GUI mode even though I can able to perform load test with GUI mode?

I'm targeting 250 TPS and able to achieve that ..I have increased my memory and monitoring CPU and memory of load generator is below 60%.

Should I go for non GUI mode ?

jmeter load-testing
2 Answers

The main limitation is that each event in the queue is being handled by a single event dispatch thread which will act as the bottleneck on your JMeter side.

My expectation is that your "250 TPS" look like:

enter image description here

while it should look like:

enter image description here

So check how does your load pattern look like using i.e. Transactions per Second listener (installable via JMeter Plugins Manager)

Also check how does your JVM look like especially when it comes to garbage collection, it can be done via i.e. JVisualVM, most probably you will see the same "chainsaw" pattern

user_28977480

You don't need to follow JMeter best practices, but

you may encounter issues to achieve specifc goals (as TPS)

  • your machine can't execute GUI or have low resources

  • you execute JMeter using a script or build tool as Jenkins

Also it's better to be familiar with JMeter CLI (non GUI) and its report capabilities

JMeter supports dashboard report generation to get graphs and statistics from a test plan.

Also it will be needed for using distributed testing

consider running multiple CLI JMeter instances on multiple machines using distributed mode (or not)

CLI also useful for Parameterising tests

The "loops" property can then be defined on the JMeter command-line:

jmeter … -Jloops=12
user_72949000
Related