Nov 6, 2024

This is the same run on the mini. The window interval is 10k here vs. 5ok, so the steps are more pronounced. Validation tracks tightly with archive (download) all the say to completion. This is also very linear (constant per block) despite the significant cost of concurrent confirmation. As described above, once confirmation drifts away from the window (about 500k) it causes a lot more paging, no longer tracking tightly with validation and archive. Once archive and validation complete, confirmation should accelerate, which is right about where the graph ends (due to an unrelated issue). Which would look similar to the complete previous (maxi) graph above. So the next effort is to try a couple ways to more closely bind confirmation to archive/validation (without tightly coupling them). Since the same result is shown on both, I'll test on the maxi which is much faster. First I'll try adjusting the confirmation chaser thread count to match that of the validator and downloader combined.