Bitcoin full node and query server

Mar 30, 2025

View in context in the libbitcoin Slack #general mirror.

evoskuil15:52
I'm hoping to get rid of most of the archival slope increase resulting from the high LF by keeping the full table FP rate under ~0.8%, as that's where it started to slow down in the milestone runs. This is a memory tradeoff, which is also a performance issue. Too far on either one is suboptimal. So this is just about finding an optimal point for the minimum RAM baseline. Above that the optimal proportion may differ, but the importance is lesser. Once we get to the maxi it barely matters.