Bitcoin full node and query server

Jun 19, 2024

View in context in the libbitcoin Slack #general mirror.

evoskuil20:21
The left section is performing unspendable_prevout reads, most of which is consumed by to_strong, which in turn is almost entirely spent in the tx hash table lookup. Since tx keys are 32 byte values, this is a (relatively) costly search. The tables is configured to 1.5 conflicts on average, but this can still cause significant paging of the body. The total actual distribution of conflict list lengths in the tx tables is:
tx: 1 frequency: 228206539
tx: 2 frequency: 171211514
tx: 3 frequency: 85657769
tx: 4 frequency: 32136386
tx: 5 frequency: 9642087
tx: 6 frequency: 2413019
tx: 7 frequency: 517115
tx: 8 frequency: 97139
tx: 9 frequency: 16368
tx: 10 frequency: 2436
tx: 11 frequency: 306
tx: 12 frequency: 31
tx: 13 frequency: 3