Capitalization for Badger.
Johnny committed
Apr 28, 2020 at 11:49 UTC
01182c18e965b68571e7c83bd9760e68baef063e
1 file changed
+2
-4
CHANGELOG.md
+2
-4
@@ -20,8 +20,6 @@ The current DHT suffers from three core issues addressed in this release:
20
- The DHT query logic doesn't properly terminate when it hits the end of the query and, instead, aggressively keeps on searching.
21
- The routing tables are poorly maintained. This can cause search performance to slow down linearly with network size, instead of logarithimicaly as expected.
22
23
-While some of the DHT improvements will be apparent on release, many of the performance improvements will become more pronounced as the network upgrades.
24
-
23
###### Reachability
24
25
We have addressed the problem of undialable nodes by having nodes wait to join the DHT as _server_ nodes until they've confirmed that they are reachable from the public internet.
@@ -112,7 +110,7 @@ To enable, run:
110
111
#### Datastores
112
115
-Continuing on with the of improving our core data handling subsystems, both of the datastores used in go-ipfs, badger and flatfs, have received important updates in this release:
113
+Continuing with the of improving our core data handling subsystems, both of the datastores used in go-ipfs, Badger and flatfs, have received important updates in this release:
114
115
##### Badger
116
@@ -134,7 +132,7 @@ Badger is complicated. FlatFS pushes all the complexity down into the filesystem
132
133
Badger can use a lot of memory. In this release, we've tuned Badger to use `~20MB` of memory by default. However, it can still produce spikes as large as [`1GiB` of data](https://github.com/dgraph-io/badger/issues/1292) in memory usage when garbage collecting.
134
137
-Finally, badger isn't very aggressive when it comes to garbage collection, and we're still investigating ways to get it to more aggressively clean up after itself.
135
+Finally, Badger isn't very aggressive when it comes to garbage collection, and we're still investigating ways to get it to more aggressively clean up after itself.
136
137
We suggest you use Badger if:
138