Jul 19, 2026

A unlimited concurrency window (0) with 12 network threads resulted in a milestone time of 29.6 mins, so it's actually faster to use the window (which is the cause of the stepping above). The above numbers of confirmation, not download. Those are loosely coupled, but because of the window closures, confirmation shares CPU times at the end of each window, and closes out conformation state. Otherwise there is a very long tail at the end of the run where all of the confirmations live, and at that point the data is no longer proximal, so a little more expensive.