Create 2019-02-11--go-core-dev-team-weekly.md #871
Conversation
ghost
assigned 
| @@ -0,0 +1,169 @@ | |||
| # 💫Golang Core Dev Team Weekly Sync 🙌🏽 2019-02-11 | |||
|
|
|||
| Please note. There has been a [meeting format change](https://github.com/ipfs/team-mgmt/issues/827#issuecomment-452157617) intended to make our brief sync time more valuable and more easily understood by new/occasional attendees. | |||
| - Summarize your next steps. | ||
| - Review other Questions/Announcements/Notes | ||
|
|
||
| ## Current IPFS Initiatives |
There was a problem hiding this comment.
Perhaps rename to "Current Go Core Initiatives" as these are representative of what this team is focusing on
|
|
||
| @magik6k - Moved go-ds-bench a bit forward, can start running serious benchmarks soon | ||
| - Needs infra: https://github.com/protocol/ad-hoc-infra/pull/24 | ||
| - This is dev-only, will need more & more diverse infra soon |
There was a problem hiding this comment.
@eingenito @magik6k Is there a requirements doc for what this benchmarking infrastructure is? Would providing 4TB to each member of the team enable you to start pulling some results?
There was a problem hiding this comment.
This is a small scale infrastructure where I want to test a diverse set of configurations, to tinker with tooling and different performance characteristics, mostly to know where 'more testing is needed'.
Testing on large data can produce interesting outcomes, but tends to be predictable from small scale data. I want to start by testing a lot of scenarios to see what will tell us the most when scaled up
| #### Bitswap | ||
| Summary: We are improving the performance of transferring data between IPFS instances: [Epic Issue](https://github.com/ipfs/go-ipfs/issues/5723) | ||
|
|
||
| - all refactor tickets are merged. cant remember if that was last week. |
There was a problem hiding this comment.
Is there benchmarks for large datasets between two nodes?
The perf improvements should be visible on the interop tests http://github.com/ipfs/interop
| #### CoreAPI | ||
| Summary: We are improving the API used to drive IPFS functionality and extracting it to a separate project without a dependency on go-ipfs itself. [Epic Issue](https://github.com/ipfs/go-ipfs/issues/4498) | ||
|
|
||
| - Interface has been extracted from go-ipfs! https://github.com/ipfs/interface-go-ipfs-core/ |
There was a problem hiding this comment.
Is there a tutorial on how to use go-ipfs through importing it as a package? Analogous to: https://github.com/ipfs/js-ipfs/tree/master/examples#tutorials
There was a problem hiding this comment.
We still need to cleanup/refactor go-ipfs constructor, which iirc is OKR this quarter
| Graphsync team is busy this week but will try to arrange some time to further discuss design | ||
| * Base32/CIDv1 (@eingenito) | ||
| Most important next milestone is storing/fetching multihashes in the DHT in libp2p | ||
|
|
There was a problem hiding this comment.
This notes are amazing! It is amazing to see progress so clearly outlined. Awesome work Go Core Team 👏🏽👏🏽👏🏽👏🏽
No description provided.