Closed tkrajca closed 8 years ago
@tkrajca ,
maintenance and development of Locust is currently in a bit of flux, so new code has not been merged recently. However, the situation should hopefully get fixed up soon.
We use these scripts internally on top of locust.io and are happy to work with the community on incorporating them into locust.io. Is this something that you would be interested in doing/having part of locust.io?
so, In the meantime, I would just go ahead and create the Pull Request with your proposed changes. (pasting code here in the issue tracker isn't really helpful) Once your changes are pushed to your repo and things are in a PR format, the code can be discussed and reviewed. Once contributions get flowing again, maintainers can triage all the open PR's and decide what to merge. You can link to your PR from this issue and remove the code snippets you pasted to make things more clear. (if you do decide to craft a PR, feel free to tag me on it for code review)
thanks!
I'm -1 on this.
Is this something that you would be interested in doing/having part of locust.io?
I don't think either utility is appropriate to include with locust.
I am closing this issue. If you want to re-open it, please submit a pull request for review... other reviewers might feel differently.
Hi guys, a while ago, I wrote two utitlities - ping.py and benchmark.py - on top of locustio==0.7.1.
Example:
Example:
We use these scripts internally on top of locust.io and are happy to work with the community on incorporating them into locust.io. Is this something that you would be interested in doing/having part of locust.io?
Cheers, Tomas
ping.py:
benchmark.py: