Hello,
Is there a way to cumulate response time of requests ?
Our case is that we have some screen which call multiple requests, and we want to show on charts the overall time for these screens.
We try to rename requests which belongs to the same screen with the same name, but Gatling compute it as the mean of values.
Thanks in advance,
Denis
Not yet. That’s the top priority feature for 1.4.0:
https://github.com/excilys/gatling/issues/322
Please be patient…
Cheers,
Stéphane
2012/10/8 DeV@n <vanpeperstraete.d@mipih.fr>
BTW, I’d like to have some feedback on this feature’s behavior.
There’s someone who asked us for groups that could overlap.
I understand how included groups could be useful, like a process being a group of pages, but I fail to see if overlapping ones could be really useful.
As it would have an impact on the DSL and the implementation, I’d like to have some opinions on this.
Please speak now or forever hold your peace!
Cheers,
Stéphane
2012/10/8 Stéphane Landelle <slandelle@excilys.com>
Nice ! We hope see the 1.4.0 soon 
Does groups overlapping means that a request can be shared for many groups ? If so, we don’t see a use case for us.
We imagine the grouping function looking like :
.group(“Welcome Screen”){
exec(
http(“request_6”)
.get(“/x.y.z/m/images/image.gif”)
.headers(headers_2)
)
.exec(
http(“request_7”)
.get(“/x.y.z/m/script.js”)
.headers(headers_7)
)
.exec(
http(“request_8”)
.get(“/x.y.z/m/i.html”)
.headers(headers_1)
)
}
Cheers,
Hi;
I’ve tried finding more informations about that feature request (overlapping), but I didn’t find anything in the given links.
Thinking a bit about it, I don’t see very well how this could be overlapping. But hierarchical grouping seems very interesting:
Process
_ Page
_ requests
By the way, (I’m sure you already did that that way in the prototype you’re speaking about, I’m more saying that to discuss the feature here, “faire avancer le schmilblick” we could say ;-))
grouping requests is actually not the addition of request times, since many requests may be running in parallel, it must be the difference between the start time of the first request, and the end time of the last running request of the group.
I mean :
XXXXXXXXXXXXXXXXXXX
YYYYYYYYYYYYYYYYYYYYYYYYYYYYY
ZZZZZZZZZ
DDDDDDDDDDDDDDDDDDD
^ End to take in account.
Cheers
2012/10/8 Stéphane Landelle <slandelle@excilys.com>
grouping requests is actually not the addition of request times, since many requests may be running in parallel, it must be the difference between the start time of the first request, and the end time of the last running request of the group.
Of course, Baptiste, you’re right 
“Cumulate requests response time” wasn’t a good idea for title !
BTW, hierarchical grouping can help us for targeting anormal big time response.
Exemple
Process : 10s
_Page 1 : 1s
_Req 1 : 1s
_Page 2 : 9s
_Req 2 : 0.5s
_Req 3 : 8s ← Black Duck here !
_Req 4 : 0.5s
Cheers
Thanks for sharing your thoughts.
I think we all agree on how to group things, so that’s how we’ll do it for 1.4.0.
Cheers,
Stéphane
2012/10/8 DeV@n <vanpeperstraete.d@mipih.fr>
+1