CHANGELOG: vyzo CR
License: MIT Signed-off-by: Steven Allen <steven@stebalien.com>
Steven Allen committed
Apr 16, 2019 at 09:11 UTC
313c0cf2a80f958090fd940317e23e196f86c474
1 file changed
+5
-5
CHANGELOG.md
+5
-5
@@ -161,7 +161,7 @@ running a public gateway, upgrading to 0.4.20 will likely fix them.
161
#### Relays
162
163
After AutoRelay was introduced in go-ipfs 0.4.19, the number of peers connecting
164
-through relays ski-rocketed to over 120K concurrent peers. This highlighted some
164
+through relays skyrocketed to over 120K concurrent peers. This highlighted some
165
performance issues that we've now fixed in this release. Specifically:
166
167
* We've significantly reduced the amount of memory allocated per-peer.
@@ -172,10 +172,10 @@ performance issues that we've now fixed in this release. Specifically:
172
rapidly forming new connections. This will actually help _all_ nodes but will
173
especially help relays.
174
175
-If you've enabled relays in go-ipfs 0.4.19 and it hasn't burned down your
176
-machine yet, this release should improve things significantly. However, relays
177
-are still under heavy load so running an open relay will continue to be resource
178
-intensive.
175
+If you've enabled relay _hop_ (`Swarm.EnableRelayHop`) in go-ipfs 0.4.19 and it
176
+hasn't burned down your machine yet, this release should improve things
177
+significantly. However, relays are still under heavy load so running an open
178
+relay will continue to be resource intensive.
179
180
We're continuing to investigate this issue and have a few more patches on the
181
way that, unfortunately, won't make it into this release.