Oct 22, 2024

It's interesting that we've been milestone syncing in under an hour for a year now, but significant interest came when I posted that we are doing it on a $356 machine. As if doing it on a 7 year old machine wasn't good. 🤔 But getting requests for validation stats now. So I've patched up the work I was doing in August and running it now on the big machine for a baseline. The above finished the first 295,000 blocks in 382 seconds. I had the blocks downloaded from an old run, and by turning off checkpoints I can force it to validate them, but since milestone state is stored with the block, these cannot be bypassed. Starting a clean run now, but that is 3.88% of the 840k block txs, which puts it on pace to complete in 2.7 hours if linear. But the overhead in small blocks is much higher, so it's on pace for around 2 hours (excluding download). We have the option to validate and download concurrently, which is optimal on big machines, because CPU is otherwise underutilized. On smaller machines it's probably best to only validate when downloads are "current". Then of course there's the confirmation step. Also, it's pointless to be validating checkpointed blocks, but it's sort of a benchmarking thing.