diff options
| author | willcl-ark <will@256k1.dev> | 2023-01-13 20:08:46 +0000 |
|---|---|---|
| committer | willcl-ark <will@256k1.dev> | 2023-01-20 13:27:07 +0000 |
| commit | ae797463dc7c72d990afa3ca53eeced7563ccd29 (patch) | |
| tree | 04dd02a9de8ab7f4cef6d1ec6f2bf25e26ce622a /doc | |
| parent | 1134686ef92fb622ac32dc7463d3763cf18c85ad (diff) | |
doc: Update blocksonly behaviour in reduce-memory
Changes to the default mempool allocation size now documented.
Provides users with guidance on the mempool implications of -blocksonly
mode, along with instructions on how to re-enable old behaviour.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/reduce-memory.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/reduce-memory.md b/doc/reduce-memory.md index 296b172bde..097cc9f001 100644 --- a/doc/reduce-memory.md +++ b/doc/reduce-memory.md @@ -16,11 +16,11 @@ The size of some in-memory caches can be reduced. As caches trade off memory usa - The minimum value for `-maxmempool` is 5. - A lower maximum mempool size means that transactions will be evicted sooner. This will affect any uses of `bitcoind` that process unconfirmed transactions. -- To completely disable mempool functionality there is the option `-blocksonly`. This will make the client opt out of receiving (and thus relaying) transactions completely, except as part of blocks. +- Since `0.14.0`, unused memory allocated to the mempool (default: 300MB) is shared with the UTXO cache, so when trying to reduce memory usage you should limit the mempool, with the `-maxmempool` command line argument. - - Do not use this when using the client to broadcast transactions as any transaction sent will stick out like a sore thumb, affecting privacy. When used with the wallet it should be combined with `-walletbroadcast=0` and `-spendzeroconfchange=0`. Another mechanism for broadcasting outgoing transactions (if any) should be used. +- To disable most of the mempool functionality there is the `-blocksonly` option. This will reduce the default memory usage to 5MB and make the client opt out of receiving (and thus relaying) transactions, except from whitelisted peers and as part of blocks. -- Since `0.14.0`, unused memory allocated to the mempool (default: 300MB) is shared with the UTXO cache, so when trying to reduce memory usage you should limit the mempool, with the `-maxmempool` command line argument. + - Do not use this when using the client to broadcast transactions as any transaction sent will stick out like a sore thumb, affecting privacy. When used with the wallet it should be combined with `-walletbroadcast=0` and `-spendzeroconfchange=0`. Another mechanism for broadcasting outgoing transactions (if any) should be used. ## Number of peers |