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

Mainflux Benchmarks #2042

Open
4 tasks
dborovcanin opened this issue Jul 19, 2023 · 3 comments · May be fixed by #2227
Open
4 tasks

Mainflux Benchmarks #2042

dborovcanin opened this issue Jul 19, 2023 · 3 comments · May be fixed by #2227

Comments

@dborovcanin
Copy link
Collaborator

dborovcanin commented Jul 19, 2023

Improve Mainflux benchmarks and load tests. We have a repo for load tests, but it is outdated. Some of the topics worth exploring:

  • Add benchmark tests in Go
  • Explore tools for distributed load testing and use them on Mainflux deployment in the cloud
  • Explore different scenarios (check the linked repo for more info):
  • Fan-in
  • Fan-out
  • Experiment with message size and frequency
  • Compare protocols
  • Explore different brokers and brokers' configs
  • Create reports that can be used for marketing and showcasing Mainflux capabilities
@dborovcanin
Copy link
Collaborator Author

@rodneyosodo
Copy link
Member

Add benchmark tests in Go

Which tool will we use to visualize and act on the results from the benchmark? For example I wrote benchmark tests for ws/dapater.go

When I used

go tool pprof -http=:8080 cpu.prof

I get this output

image

On top of my head is we need to used a better strings concatenation

@dborovcanin dborovcanin transferred this issue from another repository Dec 29, 2023
@dborovcanin dborovcanin transferred this issue from another repository Dec 29, 2023
@dborovcanin dborovcanin transferred this issue from absmach/magistrala-old Jan 10, 2024
@dborovcanin dborovcanin added this to the S4 milestone Apr 18, 2024
@dborovcanin dborovcanin assigned JeffMboya and unassigned rodneyosodo Apr 18, 2024
@JeffMboya JeffMboya linked a pull request May 13, 2024 that will close this issue
@dborovcanin dborovcanin removed this from the S4 milestone May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

Successfully merging a pull request may close this issue.

3 participants