block_log.index creation speed is suboptimal
above is especially visible when the block_log
is on a spinning drive (i.e. with high random read latency)
for fast NVMe drive:
2021-06-16T19:48:32.440 block_log.cpp:441 construct_index ] block_num: 54840072
2021-06-16T19:48:32.440 block_log.cpp:455 construct_index ] Reconstructing Block Log Index using memory-mapped IO...resume=false,index_pos=0
2021-06-16T19:54:44.569 block_log.cpp:574 construct_index ] opening new block index
2021-06-16T19:54:44.569 block_log.cpp:582 construct_index ] block_index_stat.st_size: 438720576
it takes couple of minutes, usually less than 10-15, above it was slightly over 6
same system but with block_log on a HDD drive shows I/O bottleneck, and runs for almost 12 hours.
That's block_log.index
creation itself, not the actual replay.
for HDD drive:
2021-11-12T23:46:26.872 block_log.cpp:441 construct_index ] block_num: 59123226
2021-11-12T23:46:26.872 block_log.cpp:455 construct_index ] Reconstructing Block Log Index using memory-mapped IO...resume=false,index_pos=0
2021-11-13T10:54:36.189 block_log.cpp:574 construct_index ] opening new block index
2021-11-13T10:54:36.192 block_log.cpp:582 construct_index ] block_index_stat.st_size: 472985808