Apr 30, 2023

Just ran a quick isolated test on two simple tables using a stream reader/writer replacement that cuts out the iostream and operates directly over the memory address. This is a trivial object construction on each individual read/write just as the stream reader/writer were. The query time over the full chain (all headers) is 38% of original. If this advantage carries through the other queries and data sizes, as I expect it will since the size of data is really a consequence of quantity instances not of more bytes per instance, then this will cut confirmation to ~2hrs. Confirmation is hardly hitting the disk at all now, so I'm very hopeful. I expect it to improve tx read and write proportionally as well. If so and not peer limited that would reduce sequential single peer sync time to 4 hours and would reduce sequential full chain read time to 2 hours. These are numbers that are well within limits for our targets given concurrency.