Jmeter has some limitations especially when it is run in a distributed environment. Following these guidelines will assist in creating a real and continuous load:
- . You can use the console for debugging purposes or to run a small load from it to make sure the script is running correctly. The consumes a lot of memory under heavy load, therefore the console server by itself can not sustain a heavy load.
- . Use the “Remote Start All” or “Remote Start” individual servers.
- . This means the total number of threads generated by your test plan should be less than 300. The overall number of threads running from BlazeMeter will be the total number of threads multiplied by the number of JMeterEngines. For example, a test plan with 200 threads and 4 JMeterEngines, will generate a load of 800 threads.
- as it consumes a lot of memory and can result in the console freezing or JMeter running out of memory. It is, however, safe to use the “View Result Tree” listener with only “Errors” checked.
- as they consume a lot of memory. You can view all of the real time graphs using the tab in your web interface.
- . Any errors in the test plan or the test itself will appear in the log files that are available online under the tab. For example: Out of Memory, disconnections etc.
- the local path from Data Set Config if used.
- File names should include characters, underscores or hyphens: [0-9],[aA-zZ],[_-]. File names should always .
- the Files tab prior to every test run.
Best Practice Usingfiles
If you are usingfiles, we recommend following these guidelines:
- . For example: 150210-4000t-1.jtl. Do not use spaces in the file name.
- Make sure that the and not .
- to generate the real-time reports.
- for labels identifying controllers and samplers (for example requests). If you use long names, the names themselves will take the better part of the graphs generated using the tab.