MG-2042 - Mainflux Benchmarks #2227
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
This is a feature because it adds the functionality to improve Mainflux benchmarks and load tests.
What does this do?
This PR updates the existing load tests repository, adds benchmark tests in Go, explores tools for distributed load testing on Mainflux deployment in the cloud, and explores different scenarios such as Fan-in, Fan-out, message size and frequency experiments, protocol comparisons, and different brokers and brokers' configs. It also includes the creation of reports that can be used for marketing and showcasing Mainflux capabilities.
Which issue(s) does this PR fix/relate to?
Have you included tests for your changes?
Yes, I have included benchmark tests in Go and updated load tests.
Did you document any new/modified feature?
No