-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
concurrency as users per second #25
Comments
I didn't know that Gatling has a such feature. But yeah it should not be that hard to implement. Definitely something to be added to clj-gatling. So in options you could either use However, I am not sure when I have time to implement this. PRs are always welcome ;) |
I could implement this perhaps. @mhjort could you be so kind and point me where in code to look / start? Thank you! |
Just dropping a friendly ping, I'd like this feature too :) |
Thanks for pinging. I had a quick look on this. Noticed it requires some thinking and totally forgot to answer :( Since this feature was proposed clj-gatling has got quite a lot of other new features. So they should be adapted too. One of those features is The core functionality for running the simulation is in The way simulation works now is following:
So the way to implement requests per second could be following:
I have not tested that idea so this probably needs some testing. However, this could be a one way where to start. Are you still interested @jakubholynet ? It would be great if you could work with this. |
There's also this nice little library for throttling: https://github.com/brunoV/throttler. Might not be of direct use but the token bucket idea for rate limiting could be useful. |
Thank you! I run out of time but perhaps somebody else will take the ball :-) If not, then I will the next time I have an opportunity. |
Do you think it would be an idea to specify concurrency as users per second as Gatling does?
The text was updated successfully, but these errors were encountered: