aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSuhas Daftuar <sdaftuar@chaincode.com>2017-04-11 09:28:07 -0400
committerSuhas Daftuar <sdaftuar@chaincode.com>2017-04-12 21:57:46 -0400
commitb7caa30c48eb60ef14f4746dd1617865187788b1 (patch)
treecd5afb9fada12fef84e85d8de065a177496277a8
parent55f641ca194b0090a7828b0cddd3ce829d80d9e5 (diff)
downloadbitcoin-b7caa30c48eb60ef14f4746dd1617865187788b1.tar.xz
Mention dbcache memory changes in 0.14.1 release notes
-rw-r--r--doc/release-notes.md18
1 files changed, 18 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 22452190ae..4479c1a456 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -50,6 +50,24 @@ activate at a time when no segwit transactions could be included.
Since many miners are now including the segwit commitment this concern
no longer applies.
+UTXO memory accounting
+----------------------
+
+Memory usage for the UTXO cache is being calculated more accurately, so that
+the configured limit (`-dbcache`) will be respected when memory usage peaks
+during cache flushes. The memory accounting in prior releases is estimated to
+only account for half the actual peak utilization.
+
+The default `-dbcache` has also been changed in this release to 450MiB. Users
+who currently set `-dbcache` to a high value (e.g. to keep the UTXO more fully
+cached in memory) should consider increasing this setting in order to achieve
+the same cache performance as prior releases. Users on low-memory systems
+(such as systems with 1GB or less) should consider specifying a lower value for
+this parameter.
+
+Additional information relating to running on low-memory systems can be found
+here:
+[reducing-bitcoind-memory-usage.md](https://gist.github.com/laanwj/efe29c7661ce9b6620a7).
0.14.1 Change log
=================