-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Enable bitswap to handle more requests #8233
Labels
effort/weeks
Estimated to take multiple weeks
kind/enhancement
A net-new feature or improvement to an existing feature
P1
High: Likely tackled by core team if no one steps up
Milestone
Comments
aschmahmann
added
kind/enhancement
A net-new feature or improvement to an existing feature
P1
High: Likely tackled by core team if no one steps up
effort/weeks
Estimated to take multiple weeks
labels
Jun 30, 2021
We currently have some hacked together branches that cover a bunch of the work here, but they need to be transitioned into something usable in go-ipfs master.
Next steps (in order):
|
closed by #8268 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
effort/weeks
Estimated to take multiple weeks
kind/enhancement
A net-new feature or improvement to an existing feature
P1
High: Likely tackled by core team if no one steps up
At the moment go-bitswap has fixed worker count limits for areas where we expect resource limits such as the reading from the blockstore, packaging up messages and responding to peers.
We should either make the worker limits configurable from the config file, or allow them to dynamically shrink/grow to meet network demands.
Proposed steps for now are:
The text was updated successfully, but these errors were encountered: