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

prioritize candidates in bitswap requests #148

Open
willscott opened this issue Mar 10, 2023 · 2 comments
Open

prioritize candidates in bitswap requests #148

willscott opened this issue Mar 10, 2023 · 2 comments

Comments

@willscott
Copy link
Contributor

we get a set of candidates from the indexer.
when bitswap is started my understanding is that it doesn't use these, but rather will only use them once it's finished dialing it's current swarm.

that seems inefficient

@hannahhoward
Copy link
Collaborator

this requires a change in go-bitswap. We set the "find providers" action to run immediately, but go-bitswap always starts with a broadcast. I'd really like to push back on "how we should be doing bitswap" until we really have the bandwidth to take on replacing go-bitswap.

@hannahhoward
Copy link
Collaborator

but that should be it's own issue, I agree.

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