Procedure to reduce limitations of JMeter in distributed environment, following are the guidelines will assist in creating a real and continuous load:
- Decrease resource necessity
- Find out the Scoping Rules and design consequently
- Find the JMeter logs
- Before executing scripts,find out the default browser Connectivity settings
- Reduce and limit the Number of Threads
- Don’t use functional mode
- Only use same sampler in a loop rather than lots of similar samplers, and also use variables (CSV Data Set) to contrast the sample. Possibly, use Access Log Sampler
- Use a proxy server and variables
- Fresh the Files tab earlier to every test run
- Delete the local path from CSV Data Set Config and follow file naming resolution
JMeter has some limitations especially with distributed environment. To use JMeter powerfully for testing, follow these guidelines,
Limit the Number of Threads
System’s hardware has capability to limit the number of threads which you run effectively with JMeter. It depends on how fast the server is (a faster server makes JMeter to work fast and response quickly). Due to overload of work on JMeter, each thread has to wait to get access to the CPU and more inflated the timing info gets.
Use a proxy server
The Proxy server benefits you to take out definite common elements from the recorded samples. Furthermore, it is beneficial features to record your testing.
There are some test plans essential to use different values for different users/threads. For example, If you like to test a sequence that needs a unique login for each user. This is simple to do using variables.
Decrease resource necessity
The GUI mode of the system takes a lot of computer memory under heavy load,origins performance issues.
These are some guidelines to decrease resource requirement:
- Use non-GUI mode – JMeter -n -t test.jmx -l test.jtl
- Only save the data or test resultwhich is required. JMeter could take a long time to save very detailed test results.
- Deactivate the “View Result Tree” listener during the Load test. Since it consumes more memory and origins JMeter running to run out of memory.
- Deactivate all JMeter graphs results
- Use CSV test result format.
Check the JMeter logs
Any errors of the test plan or test execution should be recorded in the log files. Checking the log file assist you to discovery the error first.
Erase the local path from CSV Data Set Config
If you are using an existing CSV data file which you produced on your local computer, you should delete the current local path (Current path of CSV file). If you don’t delete the local path, JMeter cannot find the CSV data file on your local PC.
Follow file naming convention
Save test plan with simple file name, use only alphanumeric characters.