-
Notifications
You must be signed in to change notification settings - Fork 95
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
[ipfs/go-bitswap] provider performance issue #87
Comments
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
Finally, remember to use https://discuss.ipfs.io if you just need general support. |
Next step: @aschmahmann link this to the larger content routing issue and then close this out. |
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
Finally, remember to use https://discuss.ipfs.io if you just need general support. |
This commit was moved from ipfs/interface-go-ipfs-core@de3410b
This commit was moved from ipfs/interface-go-ipfs-core@de3410b
Currently the bitswap provider is responsible for announcing all content blocks to the DHT network. Also I can see there is a rate limiter which only takes 6 Cid at one time to avoid overwhelming the DHT.
Thus, I'm wondering it might be too slow to announce the content blocks. Assuming there are 1000 blocks, and it would take the provider 1000/6 = 166 rounds to process all blocks. It could be 166 minutes if each DHT providing takes 1 minutes in average.
Furthermore, I don't really get why we have to announce the content blocks? Is that not good enough if only doing for the root block? I notice there is no reprovide mechanism for content blocks, so I tend to believe it doesn't make sense to do providing for them.
Any comments?
The text was updated successfully, but these errors were encountered: