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

Improve bandwidth usage #9465

Open
cammellos opened this issue Nov 18, 2019 · 4 comments
Open

Improve bandwidth usage #9465

cammellos opened this issue Nov 18, 2019 · 4 comments
Assignees

Comments

@cammellos
Copy link
Member

@cammellos cammellos commented Nov 18, 2019

As a user
I want the status-app to consume less bandwidth
So I can use the app without burning through my data plan

Problem

Currently the status-app uses a large amount of bandwidth #9081 . This is likely due to how whisper works https://discuss.status.im/t/fixing-whisper-for-great-profit/1419 .

A potential solution has already been identified in the discuss post above, where a new type of nodes (waku-nodes), should be implemented which will drop the usage of bloom filters and instead use topics directly.

In the scope of this task there should be an option for the app to optionally use this waku nodes, while preserving the current functionalities of the app (real time messaging + offline messaging).

Bandwidth measurements should also be performed to quantify the improvements over whisper, ideally through automated testing.

Acceptance criteria

  • Waku nodes can be optionally used in the app
  • Current app functionalities are maintained while waku-nodes are used
  • The usage of waku nodes should result in a tangible improvement in bandwith.

Currently blocked by either nim or status-go integration of waku-nodes. status-im/status-go#1683

@oskarth

This comment has been minimized.

Copy link
Member

@oskarth oskarth commented Dec 2, 2019

@PombeirP do you have a link to the status-nim integration issue that is blocking this on the Nim side? waku/0 (including bridging) is already merged in nim-eth.

@pedropombeiro

This comment has been minimized.

Copy link
Contributor

@pedropombeiro pedropombeiro commented Dec 2, 2019

@oskarth

This comment has been minimized.

Copy link
Member

@oskarth oskarth commented Dec 3, 2019

I don't believe all (perhaps even most?) of those issues are a blocker for getting experimental Waku support in the app and testing that it works end to end, with bridging etc.

@pedropombeiro

This comment has been minimized.

Copy link
Contributor

@pedropombeiro pedropombeiro commented Dec 3, 2019

Yeah, the most important right now are in the Regarding wrapper/API implementation section, as well as successfully integrating libnimbus.a into libgojni.so (which I'm currently working on).

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

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.