Mempool is the piece of memory, where the client software keeps unconfirmed transactions, before they are minted in a block.
The client software ships with the default size set at 300MB. It is important to understand, that this size relates to the transactions when they are kept in memory, and in that state, transactions occupy several times more memory, than when in a block. This means that a mempool of 300MB of RAM size, is only able to keep 30 to 50MB of transactions.
When the mempool fills up, the min fee is increased for new transactions to be included in mempool and relayed, and when such tx arrives, some old transaction with lower fee is deleted from the mempool. This increased fee is later, when the mempool clears, reduced to default value, but this can take hours. This makes mempol of your client to be inconsistent with other clients on the network, and this means that block propagation methods used (compact blocks, xthin, graphene) are not efficient anymore.
Some data from the last stress test:
mempool, tx size, and memory usage size
https://statocashi.info/d/000000006/memory-pool?orgId=1&from=1541843648783&to=1541876316812
Transactions accepted vs rejected
https://statocashi.info/d/000000008/transactions?orgId=1&from=1541838180515&to=1541880124139
Fee estimates (not for mempool admition, but still gives you the overview of what happened)
https://statocashi.info/d/000000016/fee-estimates?orgId=1&from=1541694903018&to=1541721255959
[link] [comments]
source https://www.reddit.com/r/btc/comments/9wnln6/psa_to_node_operators_increase_the_default/
No comments:
Post a Comment