Mar 25, 2023

This of course includes primarily writes, but reads are also significant in these runs, as the block/tx inserts perform a hash table lookup for existing records in three tables (header, txs, tx). This requires ongoing reads across the entire table as deconfliction lists are walked. The extent of the tables increase from zero to 52GB during the run. But the size of the table doesn't affect the paging cost. So I anticipate that other read operations that are algorithmically constant (all of them) will perform as expected.