The JMeter Maven plugin will run the JMeter process in its own JVM. You have full control over this JVM and can set the -Xms and -Xmx as well as any 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>
</goals>
</execution>
</executions>
<configuration>
<jMeterProcessJVMSettings>
<arguments>
<argument>-DsocksProxyHost=localhost</argument>
<argument>-DsocksProxyPort=8080</argument>
</arguments>
</jMeterProcessJVMSettings>
</configuration>
</plugin>
</plugins>
</build>
[...]
</project>
+---+
