-
Notifications
You must be signed in to change notification settings - Fork 17
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
Update go-graphsync v0.8.0 #212
Conversation
6ea84a3
to
73edd81
Compare
Update to go-graphsync v0.8.0 with go-ipld-prime linksystem branch & trusted store.
73edd81
to
e07c455
Compare
Codecov Report
@@ Coverage Diff @@
## master #212 +/- ##
==========================================
+ Coverage 64.84% 64.96% +0.11%
==========================================
Files 24 24
Lines 2600 2600
==========================================
+ Hits 1686 1689 +3
+ Misses 573 571 -2
+ Partials 341 340 -1
Continue to review full report at Codecov.
|
@dirkmc what is the timing for this? Unfortunately we cannot use the latest go-data-transfer release because it relies on changes made to an older version of graphsync that is incompatible with ipld-prime v0.7.0 used in our project. Cannot run it from the commit either since there are breaking changes with go-fil-markets. So sadly we can't benefit from the changes you made until this gets in. Thanks! |
@tchardin we've been doing some performance testing of graphsync v0.8.0. You can follow the progress at #166 It seems like there may need to be further optimizations made before a newer version of graphsync can be integrated into go-data-transfer. I'd suggest you align your code with the latest release of go-data-transfer v1.7.0 which uses graphsync v0.6.4 |
Gotcha, thanks @dirkmc. So you confirm it would be faster to downgrade our project to ipld-prime v0.5.1 instead of waiting for this to get in? |
I think that's probably your best bet 👍 |
superseded by #246 |
Goals
Good news: The latest version of go-graphync and go-ipld-prime contains an important optimization to remove a bunch of unneccesary hashing when reading from local blockstores, which should cut down significantly on CPU usage
Bad news: The latest versions of these libraries contain a some important, but very breaking changes to syntax.
Good news: I'm updating them all the way to Lotus! And also, in most cases, from the point of view of the consuming libraries, they're simplifications.
Implementation
Background