Apr 25, 2024

I'm traveling for a few days, but this morning I also integrated population of the address index, which is just a few lines of code inside the store(tx) database function. There is almost nothing to that code, just serialize all outputs in a loop, sha256 each, and store each hash against the output foreign key. But the significant amount of hashing drives CPU up from < 5% to ~60%. SHANI should cut that back down to 10% or so. Neither CPU nor download or disk were maxed, but I think it was because I have network threads configured to 16, whereas I have 64 available cores. I think if I up that we'll hit max network or CPU. The run was showing almost 50% bandwidth, vs 100% without address indexing, so I anticipated a 3 hour total run. That's far better than Electrum X or Fulcrum, which measure indexation time against a local full node in terms of days!