forked from dashpay/dash
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge #1915: Fix block-connection performance regression and mempool …
…not copying tx performance improvement 0e59bad Document ConnectBlock connectTrace postconditions (Matt Corallo) 908ffd9 Switch pblock in ProcessNewBlock to a shared_ptr (furszy) 7b38f64 Make the optional pblock in ActivateBestChain a shared_ptr (furszy) 4cf6550 Create a shared_ptr for the block we're connecting in ActivateBCS (Matt Corallo) 140446c Keep blocks as shared_ptrs, instead of copying txn in ConnectTip (Matt Corallo) 9a809a2 Add struct to track block-connect-time-generated info for callbacks. (furszy) 80a94df Migrating to CTransationRef second round: (furszy) 2a89063 Initial mempool migration to using CTransationRef instead of a CTransation copy. (furszy) bdd5221 Add support for unique_ptr and shared_ptr to memusage (Pieter Wuille) Pull request description: Made my own way up to be able to back port bitcoin#9014. This will mean a performance regression fix over the block-connection process + less memory usage storing `CTransactionRef` instead of a plain `CTransaction` copy in the mempool. The first three commits are essentially covering: 1) mempool: using `CTransationRef` instead of coping each transaction. 2) validation: ATMP and ATMPW migrated to receive `CTransationRef`. 3) net_processing: ProcessMessage migrated TX message processing to use `CTransactionRef`. 4) swiftx: ProcessMessage migrated IX message processing to use `CTransactionRef`. 5) migrated mapOrphanTransactions to use `CTransactionRef`. And from [085dc57](085dc57) starts btc/9014 back porting work. ACKs for top commit: random-zebra: tested ACK 0e59bad Fuzzbawls: ACK 0e59bad Tree-SHA512: 96d2c77750f5b90a52d688f91b04bf04c198b1c9fa90731d848f48564cd88a8205fa278e78aa519bdc412eae7b189e96c4f52337b8965895b9634a0ad1d3a9b5
- Loading branch information
Showing
19 changed files
with
173 additions
and
128 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.