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

Collection for IPFS Weekly 7 (March 7th--March 14th) #27

Closed
RichardLitt opened this Issue Mar 9, 2016 · 7 comments

Comments

Projects
None yet
6 participants
@RichardLitt
Member

RichardLitt commented Mar 9, 2016

No description provided.

@RichardLitt RichardLitt changed the title from Collection for IPFS Weekly #7 (March 7th--March 14th) to Collection for IPFS Weekly 7 (March 7th--March 14th) Mar 9, 2016

@bergie

This comment has been minimized.

Show comment
Hide comment
@bergie

bergie Mar 10, 2016

https://github.com/the-grid/jsjob-ethereum is an experiment at creating a computational market on top of Ethereum. Computational jobs are run in a JavaScript sandbox, and both input data, the algorithm to run, and the produced results are shared over IPFS.

bergie commented Mar 10, 2016

https://github.com/the-grid/jsjob-ethereum is an experiment at creating a computational market on top of Ethereum. Computational jobs are run in a JavaScript sandbox, and both input data, the algorithm to run, and the produced results are shared over IPFS.

@bergie

This comment has been minimized.

Show comment
Hide comment
@bergie

bergie Mar 14, 2016

https://github.com/c-base/ipfs-ringpin is a set of tools for setting up an IPFS "file pinning ring" between multiple parties. Can be used for example for hackerspaces to provide redundancy by pinning each other's files.

bergie commented Mar 14, 2016

https://github.com/c-base/ipfs-ringpin is a set of tools for setting up an IPFS "file pinning ring" between multiple parties. Can be used for example for hackerspaces to provide redundancy by pinning each other's files.

@lgierth

This comment has been minimized.

Show comment
Hide comment
@lgierth

lgierth Mar 14, 2016

Member

I don't have anything good for the weekly right now -- would have to put lipstick on the pig :)

Member

lgierth commented Mar 14, 2016

I don't have anything good for the weekly right now -- would have to put lipstick on the pig :)

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid

diasdavid Mar 14, 2016

Member
  • multiaddr JS impl was upgraded, now it matches go-ipfs features which means protocols whose code's required a varint https://github.com/jbenet/js-multiaddr
  • mafmt now does uTP and WebSockets validation as well
  • new libp2p-swarm released, check it out :)
Member

diasdavid commented Mar 14, 2016

  • multiaddr JS impl was upgraded, now it matches go-ipfs features which means protocols whose code's required a varint https://github.com/jbenet/js-multiaddr
  • mafmt now does uTP and WebSockets validation as well
  • new libp2p-swarm released, check it out :)
@whyrusleeping

This comment has been minimized.

Show comment
Hide comment
@whyrusleeping

whyrusleeping Mar 14, 2016

Member

A nasty bug in our networking code was fixed this week. An issue in yamux (our primary stream multiplexer) would cause code to hang when opening a new stream if there were too many in flight stream opens. As a result of this, large file transfers (ipfs refs -r, ipfs get, and so on) would hang.

IPFS 0.4.0 is now very close to shipping, we ran @dignifiedquire's randor tool quite extensively and are more confident in the repo operations that have changed since 0.3.11. The release now has a somewhat short checklist of things that are blocking the official release.

As a small side project, I started benchmarking each of our possible datastore implementations with ds-bench. The results will help us improve the performance of our storage moving forward. On that same topic, I started an experiment in new and exciting datastores and wrote a datastore implementation that can be backed by a sql database. I then spun up a postgresql database (from docker) and ran the benchmarks against it, without any sort of tuning the initial performance metrics showed that it was around three time as fast as our current on-disk datastore. (Note: the metrics are simply testing the performance of writing random 256k binary blobs to each datastore).

Member

whyrusleeping commented Mar 14, 2016

A nasty bug in our networking code was fixed this week. An issue in yamux (our primary stream multiplexer) would cause code to hang when opening a new stream if there were too many in flight stream opens. As a result of this, large file transfers (ipfs refs -r, ipfs get, and so on) would hang.

IPFS 0.4.0 is now very close to shipping, we ran @dignifiedquire's randor tool quite extensively and are more confident in the repo operations that have changed since 0.3.11. The release now has a somewhat short checklist of things that are blocking the official release.

As a small side project, I started benchmarking each of our possible datastore implementations with ds-bench. The results will help us improve the performance of our storage moving forward. On that same topic, I started an experiment in new and exciting datastores and wrote a datastore implementation that can be backed by a sql database. I then spun up a postgresql database (from docker) and ran the benchmarks against it, without any sort of tuning the initial performance metrics showed that it was around three time as fast as our current on-disk datastore. (Note: the metrics are simply testing the performance of writing random 256k binary blobs to each datastore).

@diasdavid

This comment has been minimized.

Show comment
Hide comment
@diasdavid
Member

diasdavid commented Mar 14, 2016

@haadcode

This comment has been minimized.

Show comment
Hide comment
@haadcode

haadcode Mar 14, 2016

Member

Orbit is back in active development and going through a major code base overhaul. It now uses orbit-db as it's database layer.

orbit-db is a KV-store and Event Log on top of IPFS which allows developers to use IPFS as a database. Last week orbit-db got big performance and stability improvements and is now using CRDTs for eventual consistency.

Member

haadcode commented Mar 14, 2016

Orbit is back in active development and going through a major code base overhaul. It now uses orbit-db as it's database layer.

orbit-db is a KV-store and Event Log on top of IPFS which allows developers to use IPFS as a database. Last week orbit-db got big performance and stability improvements and is now using CRDTs for eventual consistency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment