Skip to content
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

Can we add a 'wait' period between each message being sent? #40

Closed
Mac351 opened this issue Jul 15, 2020 · 3 comments
Closed

Can we add a 'wait' period between each message being sent? #40

Mac351 opened this issue Jul 15, 2020 · 3 comments

Comments

@Mac351
Copy link

Mac351 commented Jul 15, 2020

I want to simulate a situation where we have many clients, sending a message once a minute.

I'd suggest a new parameter that accepts a wait time in seconds, like wait-period and then in the worker, add a thread sleep (or similar) to wait for the required period of time.

Awesome tool by the way, thanks!

@hikhvar
Copy link
Contributor

hikhvar commented Jul 15, 2020

Instead of a wait period I think, a maximal rate per second feels more natural. In general I like this idea. Do you want to implement this feature? A PR is very welcome.

@Mac351
Copy link
Author

Mac351 commented Jul 16, 2020

I would like to try, but my initial attempts to build locally didn't work, due to not having a "make" installed. I'm not sure if I'm going to get the time to sort this out.

I also think the wait period would suit my needs better. It will emulate a sensor sending data to an IoT endpoint once a minute. How would I get this use case working using a maximal rate per second? I'd have to set it to 1/60 messages per second!

@Mac351
Copy link
Author

Mac351 commented Jul 17, 2020

I've created a PR. I tried to link it to this issue, but that didn't work!

The docker support is really excellent. The build and run process in docker made life so simple!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants