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

feat: Measure impact between protocols #3060

Open
4 tasks
Tracked by #3069
Ivansete-status opened this issue Sep 26, 2024 · 0 comments
Open
4 tasks
Tracked by #3069

feat: Measure impact between protocols #3060

Ivansete-status opened this issue Sep 26, 2024 · 0 comments
Assignees
Labels
effort/weeks Estimated to be completed in a few weeks

Comments

@Ivansete-status
Copy link
Collaborator

Problem

nwaku supports multiple streams/protocols. Nevertheless, we need to measure how they can impact each other.

Suggested solution

Considering the current tools we have to measure the normal bandwidth and rate request, through Grafana/metrics, we should be able to see the possible impact to a any protocol when increasing the bandwidth/rate of one protocol

Acceptance criteria

  • See how a protocol can impact other protocols. The protocols to analyze are: store, lightpush, and filter.
  • Measure the current limit of each protocol separately. When it starts to have poorer performance
  • Measure the limit when two or more protocols are being compromised. See if they differ from the previous point.
  • Based on previous measures, apply the limitation per protocol, or globally.

Epic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort/weeks Estimated to be completed in a few weeks
Projects
Status: To Do
Development

No branches or pull requests

2 participants