jmeter reported memory overflow in pressure measurement process, there are many possible reasons. Pay attention to the following three points:
1, click the pressure measurement process using too many threads, the official website recommended 1000-2000. Specific look at the situation and launch applications configured machine. (A single JMeter client running on a 2-3 GHz CPU (recent CPU) can handle 1000-2000 threads depending on the type of test.)
(Official website: http: //jmeter.apache.org/usermanual/jmeter_distributed_testing_step_by_step.html)
2, disposed inside the listener written to the file, then the file is not written to the detection result stored in memory with. Also be careful not to use the "View results tree" listener.
3, during operation the pressure measurement mode using no-gui, do not use the interface pressure measurements, use a command to run jmeter -n -t.
In addition to the above considerations, we can solve this problem by modifying jmeter memory settings. Here are the steps
(1) in the file which jmeter.bat modifications windows, as shown below:
(2) linux jmeter.sh download file which modified, as shown below
Show "Modify HEAP =" time (3) start - Xms512m -Xmx512m "in the JMeter batch file" is not setting a good memory, this may be misleading.
You can view jmeter memory settings are successfully jconsole.exe
----------------
Disclaimer: This article is CSDN blogger "Cautious Cautious' original article, follow the CC 4.0 BY-SA copyright agreement, reproduced, please attach the original source and link this statement.
Original link: https: //blog.csdn.net/hwhua1986/article/details/78238019