From dfc1f18f91d459b02c2ff10dc481f3d14ffdbc20 Mon Sep 17 00:00:00 2001 From: Jeromy Date: Tue, 19 Sep 2017 18:35:20 -0700 Subject: [PATCH] update version and changelog for 0.4.11-rc2 License: MIT Signed-off-by: Jeromy --- CHANGELOG.md | 22 ++++++++++++++++++++-- package.json | 2 +- repo/config/version.go | 2 +- 3 files changed, 22 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index d85352da98b..0ab2a2e6358 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,8 +4,9 @@ Ipfs 0.4.11 is a larger release that brings many long-awaited features and performance improvements. These include new datastore options, more efficient -bitswap transfers, circuit relay support, ipld plugins and more! Take a look -at the full changelog below for a detailed list of every change. +bitswap transfers, greatly improved resource consumption, circuit relay +support, ipld plugins, and more! Take a look at the full changelog below for a +detailed list of every change. The ipfs datastore has, until now, been a combination of leveldb and a custom git-like storage backend called 'flatfs'. This works well enough for the @@ -31,6 +32,22 @@ ipfs commands to take advantage of bitswap sessions. As nodes update to this and future versions, expect to see idle bandwidth usage on the ipfs network go down noticably. +The never ending effort to reduce resource consumption had a few important +updates this release. First, the bitswap sessions changes discussed above will +help with improving bandwidth usage. Aside from that there are two important +libp2p updates that improved things significantly. The first was a fix to a bug +in the dial limiter code that was causing it to not limit outgoing dials +correctly. This resulted in ipfs running out of file descriptors very +frequently (as well as incurring a decent amount of excess outgoing bandwidth), +this has now been fixed. Users who previously received "too many open files" +errors should see this much less often in 0.4.11. The second change was a +memory leak in the DHT that was identified and fixed. Streams being tracked in +a map in the DHT weren't being cleaned up after the peer disconnected leading +to the multiplexer session not being cleaned up properly. This issue has been +resolved, and now memory usage appears to be stable over time. There is still a +lot of work to be done improving memory usage, but we feel this is a solid +victory. + It is often said that NAT traversal is the hardest problem in peer to peer technology, we tend to agree with this. In an effort to provide a more ubiquitous p2p mesh, we have implemented a relay mechanism that allows willing @@ -111,6 +128,7 @@ you. - Fix bad multipart message panic in gateway ([ipfs/go-ipfs#4053](https://github.com/ipfs/go-ipfs/pull/4053)) - Add blocks to the blockstore before returning them from blockservice sessions ([ipfs/go-ipfs#4169](https://github.com/ipfs/go-ipfs/pull/4169)) - Various fixes for /ipfs fuse code ([ipfs/go-ipfs#4194](https://github.com/ipfs/go-ipfs/pull/4194)) + - Fix memory leak in dht stream tracking ([ipfs/go-ipfs#4251](https://github.com/ipfs/go-ipfs/pull/4251)) - General Changes and Refactorings - Require go 1.8 ([ipfs/go-ipfs#4044](https://github.com/ipfs/go-ipfs/pull/4044)) - Change IPFS to use the new pluggable Block to IPLD decoding framework. ([ipfs/go-ipfs#4060](https://github.com/ipfs/go-ipfs/pull/4060)) diff --git a/package.json b/package.json index af3524f5274..816502c12a0 100644 --- a/package.json +++ b/package.json @@ -469,6 +469,6 @@ "language": "go", "license": "MIT", "name": "go-ipfs", - "version": "0.4.11-rc1" + "version": "0.4.11-rc2" } diff --git a/repo/config/version.go b/repo/config/version.go index 6441aec47c9..b3cc2a01e0c 100644 --- a/repo/config/version.go +++ b/repo/config/version.go @@ -4,6 +4,6 @@ package config var CurrentCommit string // CurrentVersionNumber is the current application's version literal -const CurrentVersionNumber = "0.4.11-rc1" +const CurrentVersionNumber = "0.4.11-rc2" const ApiVersion = "/go-ipfs/" + CurrentVersionNumber + "/"