fdcf67de80
023cd5a546txgraph: add SingletonClusterImpl (mem optimization) (Pieter Wuille)e346250732txgraph: give Clusters a range of intended tx counts (preparation) (Pieter Wuille)e93b0f09cctxgraph: abstract out creation of empty Clusters (refactor) (Pieter Wuille)6baf12621ftxgraph: comment fixes (doc fix) (Pieter Wuille)726b995739txgraph: make Cluster an abstract class (refactor) (Pieter Wuille)2602d89eddtxgraph: avoid accessing other Cluster internals (refactor) (Pieter Wuille)04c808ac4ctxgraph: expose memory usage estimate function (feature) (Pieter Wuille)7680bb8fd4txgraph: keep track of Cluster memory usage (preparation) (Pieter Wuille)4ba562e5f4txgraph: keep data structures compact (mem optimization) (Pieter Wuille)bb5cb222aedepgraph: add memory usage control (feature) (Pieter Wuille)b1637a90detxgraph: avoid holes in DepGraph positions (mem optimization) (Pieter Wuille)2b1d302508txgraph: move some sanity checks from Cluster to TxGraphImpl (refactor) (Pieter Wuille)d40302fbaftxgraph: Make level of Cluster implicit (optimization) (Pieter Wuille) Pull request description: Part of #30289. This adds a few optimizations to reduce `TxGraph`'s memory usage, and makes sure that dynamic memory it uses doesn't linger after shrinking clusters. Finally, it exposes a function `GetMainMemoryUsage()` to compute `TxGraph`'s approximate memory usage. It makes the `Cluster` type abstract, with two instances (`SingletonClusterImpl` for 1-transaction clusters, and `GenericClusterImpl` for others). On my 64-bit system, I obtain the following numbers: * `SingletonClusterImpl`: 48 bytes, plus 16 bytes malloc overhead in its `unique_ptr`, plus 8-byte pointer in `m_clusters` * `GenericClusterImpl`: 104 bytes, plus 16 bytes malloc overhead in its `unique_ptr`, plus 8-byte pointer in `m_clusters`, plus 72 bytes malloc overhead inside its vectors and `DepGraph`, plus 40 bytes per transaction in those. * `TxGraphImpl::Entry`: 72 bytes per transaction * `TxGraphImpl::ChunkData`: 8 bytes, plus 56 bytes in `std::set` overhead + malloc overhead, all per chunk. * `TxGraph::Ref`: 16 bytes per transaction This overall amounts to 200 bytes per cluster, plus 64 bytes per chunk, plus 128 bytes per transaction, but only 224 bytes overall per singleton cluster. ACKs for top commit: l0rinc: code review reACK023cd5a546instagibbs: reACK023cd5a546ismaelsadeeq: reACK023cd5a546🚢 glozow: reACK023cd5a546Tree-SHA512: c957b27f47318be7c25d71453df2ae9d4e7bf21dab13b6e5e975cca122a221a99b15c584872491225785d276a9165f090675ee0f4460a2775bd3271933e3b246
Bitcoin Core integration/staging tree
For an immediately usable, binary version of the Bitcoin Core software, see https://bitcoincore.org/en/download/.
What is Bitcoin Core?
Bitcoin Core connects to the Bitcoin peer-to-peer network to download and fully validate blocks and transactions. It also includes a wallet and graphical user interface, which can be optionally built.
Further information about Bitcoin Core is available in the doc folder.
License
Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/license/MIT.
Development Process
The master branch is regularly built (see doc/build-*.md for instructions) and tested, but it is not guaranteed to be
completely stable. Tags are created
regularly from release branches to indicate new official, stable release versions of Bitcoin Core.
The https://github.com/bitcoin-core/gui repository is used exclusively for the development of the GUI. Its master branch is identical in all monotree repositories. Release branches and tags do not exist, so please do not fork that repository unless it is for development reasons.
The contribution workflow is described in CONTRIBUTING.md and useful hints for developers can be found in doc/developer-notes.md.
Testing
Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.
Automated Testing
Developers are strongly encouraged to write unit tests for new code, and to
submit new unit tests for old code. Unit tests can be compiled and run
(assuming they weren't disabled during the generation of the build system) with: ctest. Further details on running
and extending unit tests can be found in /src/test/README.md.
There are also regression and integration tests, written
in Python.
These tests can be run (if the test dependencies are installed) with: build/test/functional/test_runner.py
(assuming build is your build directory).
The CI (Continuous Integration) systems make sure that every pull request is tested on Windows, Linux, and macOS. The CI must pass on all commits before merge to avoid unrelated CI failures on new pull requests.
Manual Quality Assurance (QA) Testing
Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.
Translations
Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.
Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.
Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.