I haven’t found the answer in previous topic, also the question is quite popular. I have http client that create some application session and request resources during it.
As you can see in second exec client iterate some entities and request them sequentially.
I should emulate client does 4 requests in parallel. Client asks and waits answers, If it finishes with one request move to the next, another 3 would be waiting. And so on.
Does anybody know the recipe?
What exactly do you need?
I see collision here - “client does 4 requests in parallel” and “it finishes with one request move to the next, another 3 would be waiting”
Ok I see,
If you want 4 users each with 100 urls (400 urls total) your code should be OK, just put atOnceUsers(4) or ramp to 4 users in setUp method
If you want 4 users with total 100 urls you have to provide correct repeat value for each user, for example:
val users = 4
val records = csv(“entities.csv”).records.count - 1
Gatling can not call one scenario from within another scenario, but it can call a CHAIN from within another chain.
It looks like what you are really trying to do is have the first virtual user get a token, and all subsequent users use the same token. Is that how the application would be used in the real world? Multiple clients all using the same token? Or would each client have its own token?