CODEWITHSUNDEEP
jmeter
veera
veera

Reputation: 57

JMeter results size limit

I am running a stability test (60hrs) in Jmeter. I have several graphs in the test plan to capture system resources like cpu, threads, heap.

The size of View_Results_Tree.xml file is 9GB after 24hrs. I am afraid if jmeter will sustain for 60hrs.

  1. Is there size limit for View_Results_Tree.xml or results folder size in Jmeter?
  2. What are the best practices to be followed in Jmeter before running such long tests? I am looking for recommended config/properties for such long tests.

Thanks Veera.

Upvotes: 4

Views: 3061

Answers (3)

Abhishek Puri
Abhishek Puri

Reputation: 373

I agree with the answer provided by UBIK LOAD PACK. But in case if you need to have the results stored somewhere you don't need to worry about the size of the file. The best solution is using Grafana and Graphite (InfluxDB) for realtime reports and efficient storage.

Upvotes: 0

UBIK LOAD PACK
UBIK LOAD PACK

Reputation: 34536

There are not limits on file size in JMeter, the limit is your your disk space. From the file name, I guess you chose XML output, it is better to choose CSV output (see below another reason for that).

Besides, ensure you're not using GUI for load testing in JMeter which is a bad practice, this will certainly break your test if you do it.

Switch to Non GUI mode and ensure you follow those recommendations.

/bin/jmeter -t -n -l /results.csv

Since JMeter 3.0, you can even generate report at end of load test of from an existing CSV (JTL, not from XML format) file, see:

As you need GUI for monitoring, run Jmeter in GUI mode only for the monitoring part.

Upvotes: 1

Dmitri T
Dmitri T

Reputation: 168092

There is no results file limit as long as it fits into your hard drive for storing or in your RAM to open and analyze.

The general recommendations are:

  1. Use CSV format instead of XML
  2. Store only those metrics which you need to store, saving unnecessary stuff causes massive memory and disk IO overheads.

If you look into jmeter.properties file (located in JMeter's "bin" folder) for properties which names start with jmeter.save.saveservice i.e. 

#jmeter.save.saveservice.output_format=csv
#jmeter.save.saveservice.assertion_results_failure_message=true
#etc.

Copy them all to user.properties file, set "interesting" properties to true and others to false - that will allow to save a lot of disk space and release valuable resources for the load testing itself.

See 9 Easy Solutions for a JMeter Load Test “Out of Memory” Failure for more detailed explanation of the above recommendations and few more JMeter performance tuning tweaks.

Upvotes: 4

Related Questions