Configuring the JVM, the JMeter process runs in
The JMeter Maven plugin would run the JMeter process in its own JVM. You have the full control over the this JVM and can set THE-XMS AND-XMX as well as the command line arguments you require. We suggest that you set THE-XMS and-xmx to the same values for optimal performance.
+---+<project> [...] <Build> <Plugins> <Plugin> <groupid>com.lazerycode.jmeter</Groupid> <artifactid>jmeter-maven-plugin</Artifactid> <version>2.0.3</Version> <Executions> <Execution> <id>jmeter-tests</Id> <Goals> <goal>jmeter</Goal> </goals> </execution> </executions> <configuration> <jmeterprocessjvmsettings> <xms>1024</xms> <xmx>1024</ xmx> <arguments> <argument>-Xprof </argument> <argument>-xfuture</ argument> </arguments> </jmeterprocessjvmsettings> </ configuration> </plugin> </plugins > </build> [...] </project>+---+
SOCKS proxy configuration relies on JVM arguments, Socksproxyhost and Socksproxyport:
+---+<project> [...] <Build> <Plugins> <Plugin> <groupid>com.lazerycode.jmeter</Groupid> <artifactid>jmeter-maven-plugin</Artifactid> <version>2.0.3</Version> <Executions> <Execution> <id>jmeter-tests</Id> <goals> <goal>jmeter</goal> </< Span class= "pl-ent" >goals> </execution> </executions> <configuration> <jmeterprocessjvmsettings> <arguments> <argument>-dsocksproxyhost=localhost</ argument> <argument>-dsocksproxyport=8080</ argument> </arguments> </ jmeterprocessjvmsettings> </configuration> </plugin> </plugins> </build> [...] </project>+---+
Jmeter-maven-plugin Advanced Applications: Configuring the JVM, the Jmeter process runs in