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.

Sign up for GitHub

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

Jump to bottom

Distinguish net vs gross bandwith usage #62

Open
adklempner opened this issue Sep 28, 2024 · 1 comment · May be fixed by status-im/status-go#5973
Open

Distinguish net vs gross bandwith usage #62

adklempner opened this issue Sep 28, 2024 · 1 comment · May be fixed by status-im/status-go#5973
Assignees
@adklempner

Comments

@adklempner
Copy link
Collaborator

gross is all incoming traffic, while net-in traffic we only count messages that are to be relayed to our peers.
So if a message is not valid due to RLN proof issue or improper format/size, anything will also be counted as gross-in - not just duplicates.

Reference PR in nwaku: waku-org/nwaku#2920
@chaitanyaprem
Copy link

Along with this, it would also be good to sub-categorize the traffic based on duplicate/invalid etc. It would give us an idea if there is spamming happening or is it just gossipsub's duplicate overhead.

@adklempner adklempner self-assigned this Oct 21, 2024
This was referenced Oct 22, 2024
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@adklempner adklempner

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(telemetry)_: track total bandwidth status-im/status-go
2 participants
@chaitanyaprem @adklempner