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

Investigate moving self-addressed messages to separate shard #6234

Open
Tracked by #265
plopezlpz opened this issue Jan 2, 2025 · 0 comments
Open
Tracked by #265

Investigate moving self-addressed messages to separate shard #6234

plopezlpz opened this issue Jan 2, 2025 · 0 comments
Assignees

Comments

@plopezlpz
Copy link
Contributor

Backup/sync messages are self-addressed messages, those might be increasing bandwidth in shard 32, it could be advantageous to post them into a separate shard (e.g.: 128) via light-push and get them using store query.

The goal is to reduce bandwidth in the shard used for content messages where status desktop nodes would be participating in relay.

Also track the bandwidth saved, there is a PR that will record the bandwidth by message type here:
https://github.com/status-im/telemetry/pull/74/files
Once merged we could ideally see the gains of moving self-addressed messages to a different shard

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

No branches or pull requests

2 participants