Bitcoin full node and query server

Nov 4, 2024

View in context in the libbitcoin Slack #general mirror.

evoskuil14:27

Just to be sure it's actually reading and interpreting the values:

2024-11-04T14:25:24Z Config file arg: par="7"  <<<<<<==========
2024-11-04T14:25:24Z Config file arg: txindex="1"
2024-11-04T14:25:24Z Using at most 125 automatic connections (2048 file descriptors available)
2024-11-04T14:25:24Z Wallet disabled!
2024-11-04T14:25:24Z scheduler thread start
2024-11-04T14:25:24Z Using /16 prefix for IP bucketing
2024-11-04T14:25:24Z init message: Loading P2P addresses…
2024-11-04T14:25:24Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely…"
2024-11-04T14:25:24Z Creating peers.dat because the file was not found ("M:\Core\Validate\peers.dat")
2024-11-04T14:25:24Z init message: Loading banlist…
2024-11-04T14:25:24Z Recreating the banlist database
2024-11-04T14:25:24Z SetNetworkActive: true
2024-11-04T14:25:24Z Script verification uses 6 additional threads  <<<<<<==========

2 replies · evoskuil · last Nov 04, 2024

evoskuil16:29

What's even more interesting about this is that on the mini the validation thread count is 16 (so all hardware threads). So it's not about preserving responsiveness of the machine (though this should certainly be up to the user in any case).

evoskuil21:41

The win mini full validation run for BC is tracking at a 15 hour rate. This is consistent with my previous guess about assumevalid. Validating signatures on a sufficiently fast CPU (the mini has 16 threads and SHANI) will not slow down the run much, making it bound under the same conditions as assumevalid.