Shulou(Shulou.com)06/03 Report--

When using jmeter for stress testing, a memory overflow outfmenmory error was reported after a period of time, resulting in jmeter jamming. First, try to add JVM_ARGS= "- Xmx2048m-Xms2048m-Xmn256m-XX:PermSize=128m-Xss256k" to jmeter, but as a result, the running time increased, but in the end, memory overflow was reported. After Baidu changed the following settings as suggested by netizens, jmeter no longer stuck:

1. In windows environment, modify jmeter.bat:

Set HEAP=-Xms256m-Xmx256m

Set NEW=-XX:NewSize=128m-XX:MaxNewSize=128m

Change to:

Set HEAP=-Xms256m-Xmx1024m

Set NEW=-XX:NewSize=128m-XX:MaxNewSize=512m

As a rule of thumb, heap is set to up to half of physical memory, and the default setting is 512m. If heap is more than half of physical memory, it may be slow to run jmeter, or even memory overflow, because java eats memory and accounts for CPU.

Note: the Xmx of a JDK 32-bit computer cannot exceed 1500m, with a maximum of 1378m. Otherwise, an error will be reported when starting Jmeter:

2. In linux environment, modify jmeter.sh:

Java $JVM_ARGS-Xms1G-Xmx5G-XX:MaxPermSize=512m-Dapple.laf.useScreenMenuBar=true-jar `dirname $0` / ApacheJMeter.jar "$@"

3. If you look at the number of digits of JDK

# java-versionjava version "1.6.0y26" Java (TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot (TM) Server VM (build 20.1-b02, mixed mode) if it is 64-bit, the last line displays 64-Bit#java-versionjava version "1.6.0y26" Java (TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot (TM) 64-Bit Server VM (build 20.1-b02, mixed mode)

Jmeter video: http://edu.51cto.com/course/2324.html

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.