You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Current, when a client storing a chunk, it first get closest peers, send send out request to each and wait on all ALL responses (Ok or non-Ok) till complete and return.
This will make the flow slow when connection to one of the nodes is in problem, i.e. a response only got returned after TimeOut.
The performance can be improved by using the similar function as to expect_closest_majority_ok with the dbc spend flow, which will erturn earlier whenever received majority OK responses.
OR even being more agressive to return on the first OK response.
The text was updated successfully, but these errors were encountered:
Current, when a client storing a chunk, it first get closest peers, send send out request to each and wait on all ALL responses (Ok or non-Ok) till complete and return.
This will make the flow slow when connection to one of the nodes is in problem, i.e. a response only got returned after TimeOut.
The performance can be improved by using the similar function as to
expect_closest_majority_okwith the dbc spend flow, which will erturn earlier whenever received majority OK responses.OR even being more agressive to return on the first OK response.
The text was updated successfully, but these errors were encountered: