Use custom graphsync with PR outstanding #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Goals
Fix receiver side unneccesary hashing
Implementation
This is a real bummer - I had an outstanding PR on go-graphsync the removes the remaining hash bottle neck (ipfs/go-graphsync#166). This PR works with that branch and several other deps that pull in that branch. It should probably not be merged as is. Instead we should pull in the pr to go-graphsync and cut a new tag and work from there.
After CPU profile:
Before CPU profile:
This gives 1s drop in time spent hashing