May 10, 2024

These are actually the same graphs as the ones posted previously, but with a 50k block window applied to the run. All blocks in the window must be downloaded before it proceeds to the next step. This is clearly visible in the graphs. What stands out clearly in the lower graph, of just block archive times, is three spikes (circled). These are the result of the run allowing one incoming channel. Only outgoing channels are performance managed, so three different channels popped up and grabbed work but didn't do any. This led to a long stall, until I noticed it and reset all channels (as described above earlier). The upper graph shows bypassed validation and confirmation chasing these steps as expected.