JVM arguments are required to further control behavior of JMH. This is indispensible under Windows where it is not possible to run a benchmark with an overly long classpath without specifying -Djmh.separateClasspathJAR (available from JMH 1.20)
Setting jvmArgs of the benchmark class does not work, because the JVM argument has to be set on the initial process.
JVM arguments are required to further control behavior of JMH. This is indispensible under Windows where it is not possible to run a benchmark with an overly long classpath without specifying
-Djmh.separateClasspathJAR(available from JMH 1.20)Setting
jvmArgsof the benchmark class does not work, because the JVM argument has to be set on the initial process.