## Per-thread stack size on top of HEAP! JAVA_XSS=" -Xss228k " JAVA_DIRECT_MEMORY=" -XX:MaxDirectMemorySize=128m " JAVA_METASPACE=" -XX:MaxMetaspaceSize=128m " JAVA_METASPACE=" -XX:MaxMetaspaceSize=160m " # because of aws/s3 JAVA_OPTIONS="${GC} ${GC_DEBUG} ${JVM_DEBUG} ...
set HEAP=-Xms2g -Xmx8g -XX:MaxMetaspaceSize=512m But when I open Jmeter in GUI mode there is a message in the command line window Modify current env variable HEAP="-Xms1g -Xmx1g -XX:MaxMetaSpaceSize=256m" in the jmeter batch file So does that mean the change in the batch file...
But if you have multiple JVMs running on the same JBoss, you might want to run it via command line argument of -Xms2g -Xmx4g (or whatever your preferred start/max memory settings are. if [ "x$JAVA_OPTS" = "x" ]; then JAVA_OPTS="-Xms2g -Xmx4g -XX:MaxPermSize=256m -Dorg....
Heap usage constant, only metaspace increase, NMT diffs showed a slow but steady leak in the memory used by threads specifically in the arena allocation. I had tried to fix it by setting the MALLOC_ARENAS_MAX=1 env var but that was not fruitful. Profiling native memory allocation with jemal...