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 performance on low bandwith / Reduce extra bandwidth usage #5534

Closed
mkg20001 opened this issue Sep 27, 2018 · 2 comments
Closed

Improve performance on low bandwith / Reduce extra bandwidth usage #5534

mkg20001 opened this issue Sep 27, 2018 · 2 comments

Comments

@mkg20001
Copy link

Version information:

go-ipfs version: 0.4.17-
Repo version: 7
System version: amd64/linux
Golang version: go1.10.3

Type: question/feature

Description:

Currently I'm using IPFS on a connection that has about 400 kBit/s down and 100 kBit/s max, though values are usually much lower because it's a shared one.
Downloading files on IPFS is next to impossible, even after setting ConnMngr.HighWater/LowWater to 20/10 and adding the source node as bootstrap peer.
Would it be possible to somehow minimize the amount of "extra" bytes that need to be transferred (e.g. SECIO Handshake, DHT, etc) to a minimum?
Is there a config that would achive this? Would this require some code changes?

@eingenito
Copy link
Contributor

It's actually one of our most critical areas of active development. The prominent related issues are probably #3786, #5037, #4396 etc..

One thing you can try (if you're connected directly to the providing peer) is mentioned here: #5037 (comment).

There are other important DHT chattiness improvements under discussion: libp2p/go-libp2p#436

Running with the server profile as described here: #5013 (comment) may also help cut down on chattiness; I'm unsure about that.

@eingenito
Copy link
Contributor

Hey @mkg20001 - I'm going to close this issue, not because it's solved or anything but just because it's covered in a lot of other roll-up issues. It's also referenced from all the issues above now. Feel free to reopen if you have additional questions or information. Thanks.

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