Nov 11, 2024

The above image shows the last attempt on the mini to bind confirmation and validation closely to download using higher thread priority. This is intended to prevent thrashing by keeping the reads (validate/confirm) close to each other and to the writes. On the mini a smaller concurrency window is used (10k blocks, vs. 50k on the maxi), which is visible in the steps. This technique didn't work, as confirmation departed from the window, which resulted in thrashing and a nonlinear confirmation trajectory.