Persist mempool, arrival times, and prioritisetransaction across restarts #8433

1. 
   gmaxwell commented at 5:52 am on July 31, 2016: contributor

   Currently the mempool isn’t persisted across restarts. The historical argument against doing this is that it would make transactions immortal. Expiration now addresses that issue.

   Without preserving the mempool node behavior changes drastically across restarts which complicates production use (e.g. mining overly small/low fee blocks) as well as development testing. The lack of retention also causes the loss of txn priority modifications made with prioritisetransaction which makes the API less reliable.

2. 
   dcousens commented at 5:59 am on July 31, 2016: contributor

   Would it be worth doing this as a constant memory-disk synchronisation effort? Or simply as an action performed upon a user-initiated shutdown?
3. 
   gmaxwell commented at 6:02 am on July 31, 2016: contributor

   I’d suggest implementing it just on shutdown and see how long it takes. If its fast with a default mempool size, I’d call that done. I think it’s not critical enough to maintain that we need to sync more often, I can solicit more input from some of the other folks who mentioned wanting it.
4. 
   laanwj commented at 8:59 am on August 1, 2016: member

   Would it be worth doing this as a constant memory-disk synchronisation effort?

   That gets closer to “mempool-on-disk” which is a completely different project with different scope.

   Or simply as an action performed upon a user-initiated shutdown?

   Much less hassle to implement and low-impact. I’d say go for that.

5. laanwj added the label Mempool on Aug 1, 2016
6. laanwj closed this on Nov 2, 2016

   ---

7. DrahtBot locked this on Sep 8, 2021

Contributors
gmaxwell dcousens laanwj

Labels
Mempool