Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bitfield_distribution: Move on blocking pool and use custom capacity #5787

Merged
merged 2 commits into from
Sep 23, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion polkadot/node/overseer/src/lib.rs
Original file line number Diff line number Diff line change
Expand Up @@ -521,7 +521,7 @@ pub struct Overseer<SupportsParachains> {
])]
bitfield_signing: BitfieldSigning,

#[subsystem(BitfieldDistributionMessage, sends: [
#[subsystem(blocking, message_capacity: 8192, BitfieldDistributionMessage, sends: [
RuntimeApiMessage,
NetworkBridgeTxMessage,
ProvisionerMessage,
Expand Down
13 changes: 13 additions & 0 deletions prdoc/pr_5787.prdoc
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
title: "Move bitfield_distribution to blocking task pool and set capacity to 8192"

doc:
- audience: Node Dev
description: |
This is moving bitfield_distribution to the blocking task pool because it does cpu
intensive work and to make it snappier. Additionally, also increase the message
capacity of the subsystem to make sure the queue does not get full if there is a
burst of messages.

crates:
- name: polkadot-overseer
bump: patch
Loading