Advanced Gatling use case, is it possible?

Gatling (Open-Source)
1

Hello,

I’d want to load test a message queueing application I have written using Java and Atmosphere (https://github.com/Atmosphere/atmosphere).

The application has two interfaces:

  • a WebSocket interface to which interested clients connect and identify and wait for messages on
  • a HTTP interface for sending messages to a specific client

So what I want to do is basically (in this given order):

  1. connect 100 unique clients to the WebSocket interface (and let them wait for data)
  2. send 1000 messages to the HTTP interface randomly distributed between the clients (which means every client will get about 10 messages)
  3. measure the time between a message was sent and when it was received by the correct client

I found another thread that might touch the same issue, https://groups.google.com/forum/#!topic/gatling/jqUGJsTWwQQ, but I’m not 100% sure that’s the case.

I’m quite new to both Gatling to Scala, and even though I have read through most of the documentation I haven’t figured if this possible with Gatling at all. So, is it possible? If yes, please point me to the appropriate documentation and/or tutorial.

Regards

2

Hi,

Regarding WebSockets:
Andrew Duffy has successfully developed an unofficial support that will be refactored and merged, but probably not before september (always the same “too many things to do”).
It can’t currently wait or check for incoming messages, just open/close the connection, and send data to the server.

Regarding the “messages randomly distributed between the clients”, this can be done, but you’ll have to code some Scala. Would be much more simple to have 10 messages per users and use the DSL out of the box.

Cheers,

Stéphane

3

Hello,

Thank you for your fast response!

I had actually found Andrew Duffy’s WebSocket extension already, I forgot to mention that. But I was afraid it wouldn’t be able to do what I really need, wait and parse incoming messages. So I guess the answer to my original question is ‘no’, then?

Thanks for your suggestion. Randomly distributed isn’t really a requirement as long as the sending of messages is done concurrently.

Regards,

4

I had actually found Andrew Duffy's WebSocket extension already, I forgot
to mention that. But I was afraid it wouldn't be able to do what I really
need, wait and parse incoming messages. So I guess the answer to my
original question is 'no', then?

Currently, no.