Apr 12, 2023

Each individual operation is constant time in the byte size of the store and in count of txs. However the total time is significant just owing to the volume of inputs (2.2 billion). Basically constant time query but linear to perform a pass over the whole store (822 million txs) - since these operations cannot be made concurrent. I'll do a full run tonight, but I expect that determining confirmability for and setting confirmation state of each tx will require about 5-10 hours. That would set a floor on sync type, with or without validation. While validation can be highly parallelized, confirmation is using 100% cpu with concurrency. In other words, we would become doubly cpu bound during validation despite the concurrent nature of validation vs. confirmation.