Been using gatling for my load testing so far and its working great.
However there are a couple of problems that i faced and which are not currently implemented from what i have seen:
(1) Possibility to inject different Byte Array bodies to each individual request . The use case is i am load testing a web service that accepts protocol buffer in the HTTP Body via POST
I want to send a different one for each request.
I wanted to be able to do something like this :
I send a callback function in the scenario which is called each time the http body needs to be defined. I also needed to set the Content Length on the fly since it may vary for each request.
(2) Possiblity to use redis as a feeder for Gatling. I found it a bit tedious having to load all the data in Gatling itself before running the Simulation especially for millions of requests.
Redis allows for Mass insert of keys now : http://redis.io/topics/mass-insert . (Its crazy fast to insert millions of keys!)
I wanted to load the data to be used in a simulation on a redis list and pop out for each request and place it in the session.
This allows be to define me to define a redis backed simulation like this:
For now i’ve implemented only queue feeder , but the other two should not be too hard to implement.
I have implemented the functionality above in my fork. Although i have place everything in gatling-core right now, i believe this should be implemented as plugins outside of the core.
The relevant commits are :
(redis protocol function)
Can you please have a look and let me know if these are viable/relevant features for gatling or indeed if you think it is implemented correctly?