Skip to content

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.

Questions or feedback? You can discuss issues and obtain free support on Pantheon Gitter channel.
For paid professional support by PegaSys, contact us at [email protected]