dash/files.md at 7ff6515c8814210010bc4f4f02f32cf22d20e9d6

mirror of https://github.com/dashpay/dash.git synced 2024-12-25 12:02:48 +01:00

Merge #13033 : Build txindex in parallel with validation

9b2704777c [doc] Include txindex changes in the release notes. (Jim Posen)
ed77dd6b30 [test] Simple unit test for TxIndex. (Jim Posen)
6d772a3d44 [rpc] Public interfaces to GetTransaction block until synced. (Jim Posen)
a03f804f2a [index] Move disk IO logic from GetTransaction to TxIndex::FindTx. (Jim Posen)
e0a3b80033 [validation] Replace tx index code in validation code with TxIndex. (Jim Posen)
8181db88f6 [init] Initialize and start TxIndex in init code. (Jim Posen)
f90c3a62f5 [index] TxIndex method to wait until caught up. (Jim Posen)
70d510d93c [index] Allow TxIndex sync thread to be interrupted. (Jim Posen)
94b4f8bbb9 [index] TxIndex initial sync thread. (Jim Posen)
34d68bf3a3 [index] Create new TxIndex class. (Jim Posen)
c88bcec93f [db] Migration for txindex data to new, separate database. (Jim Posen)
0cb8303241 [db] Create separate database for txindex. (Jim Posen)

Pull request description:

  I'm re-opening #11857 as a new pull request because the last one stopped loading for people

  -------------------------------

  This refactors the tx index code to be in it's own class and get built concurrently with validation code. The main benefit is decoupling and moving the txindex into a separate DB. The primary motivation is to lay the groundwork for other indexers that might be desired (such as the [compact filters](https://github.com/bitcoin/bips/pull/636)). The basic idea is that the TxIndex spins up its own thread, which first syncs the txindex to the current block index, then once in sync the BlockConnected ValidationInterface hook writes new blocks.

  ### DB changes

  At the suggestion of some other developers, the txindex has been split out into a separate database. A data migration runs at startup on any nodes with a legacy txindex. Currently the migration blocks node initialization until complete.

  ### Open questions

  - Should the migration of txindex data from the old DB to the new DB block in init or should it happen in a background thread? The downside to backgrounding it is that `getrawtransaction` would return an error message saying the txindex is syncing while the migration is running.

  ### Impact

  In a sample size n=1 test where I synced nodes from scratch, the average time [Index writing](https://github.com/bitcoin/bitcoin/blob/master/src/validation.cpp#L1903) was 3.36ms in master and 1.72ms in this branch. The average time between `UpdateTip` log lines for sequential blocks between 400,000 and IBD end on mainnet was 0.297204s in master and 0.286134s in this branch. Most likely this is just variance in IBD times, but I can try with some more trials if people want.

Tree-SHA512: 451fd7d95df89dfafceaa723cdf0f7b137615b531cf5c5035cfb54e9ccc2026cec5ac85edbcf71b7f4e2f102e36e9202b8b3a667e1504a9e1a9976ab1f0079c4

2021-05-25 13:48:04 +03:00

1.8 KiB

Raw Blame History

banlist.dat: stores the IPs/Subnets of banned nodes
blocks/blk000??.dat: block data (custom, 128 MiB per file)
blocks/rev000??.dat; block undo data (custom)
blocks/index/*; block index (LevelDB)
chainstate/*; block chain state database (LevelDB)
dash.conf: contains configuration settings for dashd or dash-qt
dashd.pid: stores the process id of dashd while running
database/*: BDB database environment; only used for wallet; moved to wallets/ directory on new installs since 0.16.0
db.log: wallet database log file; moved to wallets/ directory on new installs since 0.16.0
debug.log: contains debug information and general logging generated by dashd or dash-qt
evodb/*: special txes and quorums database
fee_estimates.dat: stores statistics used to estimate minimum transaction fees and priorities required for confirmation
governance.dat: stores data for governance obgects
indexes/txindex/*: optional transaction index database (LevelDB); since 0.17.0
llmq/*: quorum signatures database
mempool.dat: dump of the mempool's transactions
mncache.dat: stores data for masternode list
netfulfilled.dat: stores data about recently made network requests
peers.dat: peer IP address database (custom format)
wallet.dat: personal wallet (BDB) with keys and transactions; moved to wallets/ directory on new installs since 0.16.0
wallets/database/*: BDB database environment; used for wallets since 0.16.0
wallets/db.log: wallet database log file; since 0.16.0
wallets/wallet.dat: personal wallet (BDB) with keys and transactions; since 0.16.0
.cookie: session RPC authentication cookie (written at start when cookie authentication is used, deleted on shutdown)
onion_private_key: cached Tor hidden service private key for -listenonion
guisettings.ini.bak: backup of former GUI settings after -resetguisettings is used

1.8 KiB Raw Blame History

1.8 KiB

Raw Blame History