Oct 24, 2024

Did a little more validation performing evaluation today. We have a lot of flexibility in terms of how to run it concurrently with download and/or confirmability. Presently it looks like concurrent download/validation is optimal for high CPU machines (64 thread maxi) and not for low (16 thread mini). But this is relative to how much CPU is unused during download, which is in turn a function of RAM/SSD/WAN. I've achieved 4.5 hours with maxi concurrent validation (no confirmability checks) and have hit thrashing attempting the same on the mini. With CPU generally pegged on the mini just for download, it makes more sense to defer validation until download is current. This prevents the heavy reading of validation conflicting with the heavy writing of download (and therefore thrashing due to moderate RAM), which is not achieving any boost because CPU is already maxed out.