Whenever -blocksonly is specified, there is implicitly a zero size mempool. However, there is still a non-zero value for -maxmempool which will be shared with dbcache, leading to 300 MB extra usage. Fix this.
-blocksonly should disable sharing of mempool with dbcache #9526
issue sipa opened this issue on January 12, 2017-
sipa commented at 1:00 PM on January 12, 2017: member
- fanquake added the label Mempool on Jan 12, 2017
-
dcousens commented at 4:29 AM on January 13, 2017: contributor
Maybe just make
blocksonlysetmaxmempoolto 0? -
TheBlueMatt commented at 5:03 AM on January 13, 2017: contributor
0.14 tag?
On January 12, 2017 8:29:56 PM PST, Daniel Cousens notifications@github.com wrote:
Maybe just make
blocksonlysetmaxmempoolto 0?-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/bitcoin/bitcoin/issues/9526#issuecomment-272358536
- fanquake added this to the milestone 0.14.0 on Jan 13, 2017
- jnewbery cross-referenced this on Jan 17, 2017 from issue Setting -blocksonly sets -maxmempool to zero. by jnewbery
- maflcko removed this from the milestone 0.14.0 on Jan 27, 2017
-
maflcko commented at 11:27 PM on January 27, 2017: member
Remove the 0.14 milestone for this, because the pull that tries to fix this issue is not tagged for 0.14 and needs some more work.
- maflcko added the label Resource usage on Aug 4, 2022
- willcl-ark cross-referenced this on Nov 8, 2022 from issue Reduce default mempool size in -blocksonly mode by willcl-ark
- fanquake closed this on Jan 22, 2023
- sidhujag referenced this in commit 7613a0173d on Jan 23, 2023
- bitcoin locked this on Jan 22, 2024
