Reports display really short reponse time.


After struggling a few days with that Websphere-Cookie issue, I finally managed to run a few gatling test.
The requests are correctly sent, (and already allowed us to pin-point a multithread bug in the application =D ),
and the responses appear to be OK ; no exception in my server log, and Gatling extracts the expected values from the response body without issue.

However, the report seems wrong : all the reported response times are under 1ms.
For example, I have one request that loads and displays a shitload of data ; for some cases, it takes between 2 and 4 seconds to load everything. (time recorded inside Firefox with Firebug)
But when I run with Gatling the same request on these same cases, reports indicate that the response time is under 1ms, 0.04ms according to the Reponse Time during Simulation graph.

Has anyone ever run into that kind of issue?
What could have I missed or misunderstood?

Thanks in advance,


Even if 1ms seems actually very small, just a small guess: Gatling works at the network level. So, if your data takes actually not much time to download, but quite a lot to render inside the browser, that could be a part of the explanation?

My 2 cents,

– Baptiste


I’ve thought about that one too, especially since we have some issues with the slowness of the Javascript on some version of IE,
but Firebug does display 2~3s “waiting” and a only few milliseconds of javascript processing.
My server logs also displays way more than a few ms of processing,

Mmmm strange,

How are the times in your simulation.log file? Are they correct?


What is the format for the simulation.log ?
I guess the times are milliseconds, but I don’t know which column represents which value.

Anyway, I’ve run a simulation with one user executing one set of query on a really heavy use case.
For example, the two most heavy queries

ACTION moralEmployerSearchByMatriculeDisplaySynthesis 1 moralEmployerSearchByMatricule 1352891718279 1352891722282 1352891722282 1352891718280 OK
ACTION moralEmployerSearchByMatriculeDisplaySynthesis 1 moralEmployerDisplaySynthesis 1352891722283 1352891728206 1352891728277 1352891722284 OK

On Firefox (monitoring with firebug)
moralEmployerSearchByMatricule : 2.9s
moralEmployerDisplaySynthesis : 2.39s

It might be worth noting I’m still using the 1.4 snapshot you provided me on the other thread. =)

Found it!
In 1.4, we’re doing some clean up in the log file format, and there was a small mistake there:

Cloudbees is currently building a new snapshot.

Thanks for reporting,


I’ve tested this new snapshot, and the report looks a lot more like expected. =)

Thanks for the really fast fix!


Great news!