Author: Multipool Admin 2015-10-19 22:24:11
Published on: 2015-10-19T22:24:11+00:00
A user on the bitcoin-dev mailing list reported experiencing a memory usage issue that was not caused by connected nodes, as they were only connected to three nodes which they controlled. Another user reported a similar issue with 35 GB of RSS usage, leading to speculation that the issue is related to CreateNewBlock() and getblocktemplate. Testing with PR #6410's better mempool reporting suggests that actual in-memory usage by CTxMemPool is about 2.5x to 3x higher than serialized transaction sizes, but the excess memory usage seen in this case is on the order of 100x higher than the mempool "bytes" value, making it unlikely that this is normal/correct mempool behavior. The user suggested mitigating the mempool growth by setting -mintxfee. The user also reported on some additional notes on the issue, including valgrind not showing anything super promising. The user apologized for any confusion caused by cross-posting and promised to post more clearly in the future.
Updated on: 2023-06-11T00:07:55.488928+00:00