raspibolt icon indicating copy to clipboard operation
raspibolt copied to clipboard

Published 20 hours ago • verified publisher icon raspibolt

Increase default mempool to 2 GB

Open Bitcoinite opened this issue 1 year ago • 4 comments

Recently we have seen many node operators struggling with transactions that are't broadcasted due to being below the purging limit. If a (force) close transactions fee rate is below the purging limit, the node will drop it immediately and therefore it won't be broadcasted at all. We should increase the default mempool size significantly to mitigate this issue.

I'm open to discuss the ideal default size that we should recommend during the initial setup. The 2 GB I'm proposing is just what I have set on my own node.

Bitcoinite avatar Jan 04 '24 12:01 Bitcoinite

Important to say how much RAM you have available. A 4GB computer would probably struggle with this.

openoms avatar Jan 04 '24 12:01 openoms

Do we have any data or estimations on what RPi model most node operations are actually using? Maybe now is the time to discuss whether it is necessary to have at least 8GB of RAM in order to be able to operate a proper lightning node in such a mempool environment?

We might want to change the recommendation at the beginning of the guide to 8GB: https://github.com/raspibolt/raspibolt/blob/master/guide/raspberry-pi/preparations.md#hardware-requirements

Also we could add a remark (telling that you might comment out the maxmempool line if you are running a 4GB model) here: https://github.com/raspibolt/raspibolt/blob/master/guide/bitcoin/bitcoin-client.md#configuration

Bitcoinite avatar Jan 04 '24 12:01 Bitcoinite

2 GB is definitely overkill and a lot of people will struggle with this. Mempool.space currently shows 1.24 GB, but that includes even 1 sat/vB transactions.

Also, no Bitcoin software should even attempt to broadcast a transaction that's below current mempoolminfee of bitcoind.

I'm running RaspiBolt on different ARM hardware with 4 GB RAM. Have default 300 MB mempool, haven't experienced any issues because of that.

kristapsk avatar Jan 04 '24 13:01 kristapsk

https://jochen-hoenicke.de/queue/#BTC,24h,weight

600MB seem to be sufficient (for now).

blckbx avatar Jan 21 '24 08:01 blckbx

This pull request is marked as stale because there was no activity for 90 days. If the pull request stays inactive, it will be closed automatically in 30 days.

github-actions[bot] avatar Apr 20 '24 08:04 github-actions[bot]

This pull request has been closed due to inactivity.

github-actions[bot] avatar May 20 '24 08:05 github-actions[bot]