Load Test execution using Gatling Maven plugin script reports response times higher

Hello Gatling experts,

I have noticed high response times when running Load test for 1000 users using Maven Gatling plugin shown as 12-15 secs.

project xmlns=“http://maven.apache.org/POM/4.0.0” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance” xsi:schemaLocation=“http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd”>



UTF-8 ${project.version} 2.0.0 io.gatling.highcharts gatling-charts-highcharts ${gatling.version} test io.gatling gatling-maven-plugin ${gatling-plugin.version} test execute

-XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms4096m -Xmx4096M -Xmn100M -XX:+HeapDumpOnOutOfMemoryError -XX:+AggressiveOpts -XX:+OptimizeStringConcat -XX:+UseFastAccessorMethods -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv6Addresses=false

however when running same test using Gatling 2.1.4 (using bin/gatling.sh) on Same Ubuntu server with same OS Tuning settings (eg: Max no of files) and same test site, load test response times were shown very low. less than 1 sec.
please could you advise if i need to update pom.xml, that I am using for Maven Gatling plugin.

Thanks & Regards,

You’re comparing Gatling 2.1.4 and 2.0.3. Your issue has nothing to do with the maven plugin.
Just upgrade.

Then, 12-15 sec vs <1s seems weird. I wouldn’t expect such a performance difference. Are you sure you’re not facing some cache misses that were fixed in between (so caching wouldn’t work with 2.0.3 but would be working properly with 2.1.4)? Try disabling caching in 2.1.4 and see if you get the same results as with 2.0.3. If not, we indeed did a good job with 2.1 :wink: