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

How to interpret Messages / Client value from the report. #65

Open
carlospsikick opened this issue Feb 13, 2021 · 1 comment
Open

How to interpret Messages / Client value from the report. #65

carlospsikick opened this issue Feb 13, 2021 · 1 comment

Comments

@carlospsikick
Copy link
Contributor

Hello:
this is not a big deal, but I'm finding something a little confusing in the report output. When, for example, I run the program with -num-clients 10 -num-messages 10

The report shows Messages / Client: 100 , that is the total number of messages (clients * messages)

My expectation is that this value would be the same as --num-messages to reflect the configuration of that run.

Sample output:

# Configuration
Concurrent Clients: 10
Messages / Client:  100

# Results
Published Messages: 100 (100%)
Received Messages:  100 (100%)
Completed:          10 (100%)
Errors:             0 (0%)

If this is something that should be fixed, I'll be happy to make the PR with the adjustment (it should be minimal), but if I'm understanding this wrong, please disregard.

All the best

@hikhvar
Copy link
Contributor

hikhvar commented Feb 13, 2021

This is a valid concern. I'm currently in the process of planning a major refactoring of this stresser. One point is to generate machine readable output for post processing. While implementing that output, I will most probably refactor the current human readable output as well.

See this project https://github.com/inovex/mqtt-stresser/projects

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

No branches or pull requests

2 participants