CipherLabs
/
besu
mirror of https://github.com/hyperledger/besu
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
An enterprise-grade Java-based, Apache 2.0 licensed Ethereum client https://wiki.hyperledger.org/display/besu
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1063 Commits
44 Branches
214 Tags
201 MiB
 
 
Tag: Branch: Tree: 13249a20fd
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '13249a20fd'
${ noResults }
besu/docs/Using-Pantheon/Transactions/Transaction-Pool.md

1.3 KiB
Raw Blame History

Transaction Pool

Options and methods for configuring and monitoring the transaction pool include:

Once full, the Pantheon transaction pool accepts and retains local transactions in preference to remote transactions. If the transaction pool is full of local transactions, the oldest local transactions are dropped first. That is, a full transaction pool continues to accept new local transactions by first dropping remote transactions and then by dropping the oldest local transactions.

Decreasing the maximum size of the transaction pool reduces memory use. If the network is busy and there is a backlog of transactions, increasing the size of the transaction pool reduces the risk of transactions being removed from the transaction pool.