perf(consensus): Run broadcast routines out of process (backport #318… #135
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…0) (cometbft#3477)
Run broadcast routines out of process. Right now each broadcast routine blocks the consensus mutex for roughly
num_peers * process_creation_time
, which is genuinely notable! This PR reduces the consensus blocking overhead to just beprocess_creation_time
.On the latest osmosis branch with improvements, thats 20s of blocking time out of 140s (over the course of 1 hour. This 140s includes block execution!)
Note that WAL write time should go significantly down with open PR's. For
HasVote
, this is a meaningful increase to consensus mutex lock time, so its worth reducing.PR checklist
.changelog
(we use unclog to manage our changelog)docs/
orspec/
) and code comments - I don't know of any related docs hereThis is an automatic backport of pull request perf(consensus): Run broadcast routines out of process cometbft/cometbft#3180 done by Mergify.
PR checklist
.changelog
(we use unclog to manage our changelog)docs/
orspec/
) and code comments