Why does gatling spawn a new java process that has it's own -Xmx setting?

my long-running test is running out of heap memory, and i notice that gatling spawns a java process that seems to have it’s own idea of what ‘-Xmx’ should be:

gatling 3797 3792 62 14:46 pts/1 00:00:01 /usr/lib/jvm/jdk-17-oracle-x64/bin/java -Xms2G -Xmx8G -Dtarget=https://host.company.io:8443 <-D options removed> -Xms2G -Xmx8G -cp /home/gatling/gatling_395/active/lib/* io.gatling.bundle.GatlingCLI --run-mode local -rsf /home/gatling/gatling_395/active/user-files/data -s com.company.agentSimulation

gatling 3822 3797 99 14:46 pts/1 00:00:03 /usr/lib/jvm/jdk-17-oracle-x64/bin/java -server -XX:+HeapDumpOnOutOfMemoryError <-D options removed> -XX:MaxInlineLevel=20 -XX:MaxTrivialSize=12 -Xmx1G -Xss100M -Xms2G -Xmx8G -jar /tmp/gatlingbooter10429407521715669186.jar io.gatling.compiler.ZincCompiler

can someone shed some light on what this is about?


To isolate launcher (maven, gradle, sbt, bundle), compiler (Java, Scala, Kotlin) and Gatling runtime processes (avoid classloader and JIT pollution, different JVM options, etc).

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.