Bitcoin full node and query server

Apr 29, 2024

View in context in the libbitcoin Slack #general mirror.

evoskuil01:27

There is some room for compression in cases where flags and values are byte-aligned and can be merged in a few tables. The above also excludes validation metadata which is 100% prunable (and isn't very large). The address index and its header are ~115GB, which is reportedly smaller than Fulcrum and larger than ElectrumX, though I'm not certain about those references.

1 reply · evoskuil · last Apr 29, 2024

evoskuil14:24

Turns it that the ElectrumX ~25% size advantage is a result of partial key storage (11 vs. 32 bytes). This has the effect of increasing hash table conflicts 3 fold, but far worse, it causes the potential conflicts to have to be read, serialized and hashed for key comparison. This huge performance tradeoff for a modest space savings is way not worth it. In benchmarks it underperforms in query by orders of magnitude.