I am currently evaluating tool to load/performance test our application. Gattling looks really cool, but I have a few questions
- Our app is not http based - instead clients send XML messages over sockets. Could we do this with Gattling?
There are lot of examples that show things like
.exec( http(“Get Homepage”).get(“http://github.com/excilys/gatling”) )
Would it be possible for us to write our own stuff to put inside exec() instead of http?
If so, how would we go about that?
Would Gattling still handle collection of statistics for reports, or would we need to implement that too?
- The Grinder has support for scaling out to multiple load generation machines.
I know that Gattling does not support that out of the box and you have to collate the results manually - can anyone give more detail on how to do that?
1) Protocol support
We have design the DSL and the underneath APIs so that the execution API,
the protocol API, the statistics API and the charts API are decoupled.
So yes, you can write your own protocol API implementation and reuse the
We have yet to document it properly.
We'll do it in the next days (we're currently attending a conference).
2) Manual kind-of clustering
Does this help?
1) That sounds good - we are currently trying to figure out the API by
looking at the source code for the http implementation, and finding it
a bit confusing. (That we are new to scala probably doesn't help).
Would you have time to give us some quick pointers in lieu of
Here’s an embryo of a documentation:
Does this help you a bit?
2012/5/1 Perryn Fowler <email@example.com>
James Gregory is currently working on documenting this for ThoughtWorks:
Note that this is a WIP, too.
2012/5/2 Stéphane Landelle <firstname.lastname@example.org>
Haha - James is doing that because I asked him to - we have come full circle
I had guessed so, but wasn’t sure
2012/5/3 Perryn Fowler <email@example.com>