Don't allocate in BTreeMap
when only one postbox is needed
#819
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.
We keep track of
MsgBlkChain
s in aBTreeMap
today. Sadly this isn't a type which we can preallocate a desired capacity in and store per-CPU. As a result, for flamegraphs in the Rx pathway we can see a moderately chunky call intokmem_alloc
withinPostbox::post
for chains which have one recipient.This PR special-cases the single-recipient case so that we hold onto one chain and key on the heap until needed.