I have a Gatling scenario in which, for each user, I need to execute some preliminary steps on the system using Selenium/headless Chrome via execute {session => …}. This takes about 30 seconds for a single user. I noticed that only one Chrome instance is active at a time, suggesting that the exec block is synchronized somehow. Even with two users, the second user waits until the first user finishes that block.
Is there some kind of synchronization at play? Any way to work around it?
Yes, because I suspected it was the reason for other users being blocked, and not blocking the execution thread. I forgot how Gatling works
Thanks for the explanation.