Spike in active request when my load test is finished

I am new to Gatling and so far I really like it. Though I am having a weird issue. I am load testing some webpages and I am just looking for some measurements on the RPS. The test I have runs as expected, but when the test is over the Active Request on my web servers take a huge spike for a few seconds. It is not a big deal in the testing environment, but I am trying to load test in production and we can’t take those spikes. So you can see below I put in a jumpToRps(0), but while the request do drop to 0 the spike still happens.

Any suggestions are appreciated.

setUp(
scn.inject(
(constantUsersPerSec(50) during(115))
)
.protocols(httpConf))
.throttle(
reachRps(150) in (30 seconds),
holdFor(30),
jumpToRps(300),
holdFor(30 seconds)
jumpToRps(20),
holdFor(30)
jumpToRps(0),
holdFor(30)
)

Which version do you use?

I am on 2.1.2.

Have you enabled debug logging in order to see what is happening?

Also, how many failures are you experiencing, if any?

What probably happens is that #2415 is not enough.

Stay tuned!

no errors.

Fixed! https://github.com/gatling/gatling/issues/2508

Thanks for reporting!

awesome. Thank you.

ok now that it is committed to github how do I compile it?

Sorry, I’m a devops guy and not a developer.

Do you use the zip bundle, or another packaging?

I grabbed the zip bundle.

You have 2 solutions, until we release 2.1.4 (in ~2 weeks).

First, you can grab from our continuous integration: https://oss.sonatype.org/content/repositories/snapshots/io/gatling/highcharts/gatling-charts-highcharts-bundle/

But this is 2.2.0-SNAPSHOT, so there’s a few differences with the Gatling (2.1) you’re using, see https://github.com/gatling/gatling/issues/2504

Or, you can build from sources.
See doc: http://gatling.io/docs/2.1.3/developing_gatling/building_gatling.html#getting-the-source

Note that you have to change branch from git (git checkout 2.1.x) on both projects.

Cheers,

Stéphane

I was daydreaming… This fix as shipped in 2.1.3, that we released last Monday.
BTW, subscribing to this mailing list messages or following our Twitter account would automatically let you know when we release and what is shipped.