A memory overflow outfmenmory error occurred after a period of stress testing using jmeter, causing JMeter to die, first attempting to add jvm_args= "-xmx2048m-xms2048m-xmn256m-xx" in Jmeter.bat :P ermsize=128m-xss256k ", but the result running time increased, but eventually reported memory overflow, Baidu after following the suggestion of the netizen changed after JMeter no more cards:
1, in the Windows environment, modify the Jmeter.bat:
Set Heap=-xms256m-xmx256mset new=-xx:newsize=128m-xx:maxnewsize=128m to: Set heap=-xms256m-xmx1024mSet new=-xx:newsize=128m-xx:maxnewsize=512m
Note: JDK32-bit computer xmx cannot exceed 1500m, Max 1378m. Otherwise, an error occurs when you start the JMeter:
2, the Linux environment, modify the jmeter.sh:
Java$JVM _args-xms1g-xmx5g-xx:maxpermsize=512m-dapple.laf.usescreenmenubar=true-jar ' dirname '/apachejmeter.jar ' [ Email protected] "3, if you look at the number of bits in the JDK
# java-version
Java Version "1.6.0_26"
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 bits, the last row shows 64-bit
#java-version
Java Version "1.6.0_26"
Java (TM) SE Runtime Environment (build 1.6.0_26-b03)
64-bit Server VM (build 20.1-b02, Mixed mode)
JMeter Learning (28) Memory Overflow workaround