Nov 6, 2024

On this machine the attempt at coupling increases overall time because there is sufficient RAM to overcome thrashing, even with 64 threads. The plot shows jags at 50k intervals (the window size), which also increases total time on this machine. Validation holds closely to archive (download) constrained only by higher thread priority. Confirmation drifts away, fairly continuously, despite the highest thread priority and equal number of pooled threads (the the validator). I just realized that it might have made more sense to use a number of threads equal to the validator plus downloader. The plot also shows the effect of one stage completing (archive first, causing a slight acceleration for validation, and then validation, causing a significant acceleration for confirmation. The confirmation priority drift is the cause of the most important observation, of the inflection point in confirmation around block 550k. What we would expect on a 1TB RAM machine is that this line stays fairly straight once blocks are full. But it is decelerating until the point where validation ends (without validation this line is straight).... https://libbitcoin.slack.com/files/U6N3S6GPQ/F0803PWNVH6/image.png