Finalize blocks in parallel with contextual validation #9162
Labels
A-concurrency
Area: Async code, needs extra work to make it work properly.
A-state
Area: State / database changes
I-slow
Problems with performance or responsiveness
P-Low ❄️
Motivation
When non-checkpointed blocks are committed to a best chain in the non-finalized state with over 99 blocks (max_block_reorg_height), Zebra will remove the root of the non-finalized part of the best chain from the non-finalized state and will block contextual validation of the next block on adding it to the finalized state.
The write block task is often the critical constraint limiting initial sync performance, and is generally difficult to further parallelize as note commitment tree updates must happen in sequence.
Design
The text was updated successfully, but these errors were encountered: