I have a scénario.
The run is OK but i have a java crash memory during the report generation.
So, the report is not generated and a dump file java_pid3036.hprof is present
In attached my simulation.log that causes the crash.
I don’t attach the .hprof in group because 534 Mo. Tell me if we need it.
I tested several versions of gatling 2.0. The crash is also present on yesterday snapshot.
Thanks for you help.
simulation.zip (185 KB)
Here a link to a biggest simulation.log of another run for the same scenario with more users :
But then, the root of the problem is that you have ~14.000 different request names!!!
Gatling reports will be pretty useless then.
I love to push and also stress Gatling in their limits !!
Thanks for the fix.
I’ll test soon the last snapshot that day.
I tested the generation :
I have others runs with more users than the second one.
So, i realize now that this huge number of request names.
I will change my strategy to reduce the request name number that becomes not acceptable.
Gatling reports were definitively not designed for this.
Could you elaborate about your use case, please?