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 not 100% completed with mqtt-stresser #39

Open
bcw104 opened this issue Jan 20, 2019 · 1 comment
Open

can not 100% completed with mqtt-stresser #39

bcw104 opened this issue Jan 20, 2019 · 1 comment

Comments

@bcw104
Copy link

bcw104 commented Jan 20, 2019

https://github.com/inovex/mqtt-stresser

@bcw104
Copy link
Author

bcw104 commented Jan 20, 2019

.\mqtt-stresser-windows-amd64.exe -broker tcp://127.0.0.1:1883 -num-clients 100 -num-messages 150
-rampup-delay 1s
100 worker started
..................................................................................................Test timeout. Wait 5s to allow disconnection of clients.

Configuration

Concurrent Clients: 100
Messages / Client: 15000

Results

Published Messages: 15000 (100%)
Received Messages: 14998 (100%)
Completed: 98 (98%)
Errors: 0 (0%)

Publishing Throughput

Fastest: 18749 msg/sec
Slowest: 482 msg/sec
Median: 1853 msg/sec

< 2309 msg/sec 57%
< 4136 msg/sec 61%
< 5962 msg/sec 76%
< 7789 msg/sec 80%
< 9615 msg/sec 88%
< 11442 msg/sec 93%
< 13269 msg/sec 97%
< 15095 msg/sec 99%
< 20575 msg/sec 100%

Receiving Througput

Fastest: 3334 msg/sec
Slowest: 105 msg/sec
Median: 120 msg/sec

< 428 msg/sec 97%
< 750 msg/sec 99%
< 3657 msg/sec 100%

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

1 participant